Error Handling Question

I am writing a java program which will run as an automated job. There won't be a user sitting there watching it. If it throws an exception where should I put it? Normally I do
catch (Exception e){
e.printStackTrace();
But that won't do any good if it's running automatically. How do I set System.err path?
Is there a way for me to print the stack trace into a log file?

You can use System.setErr() (or something like that).
Or you can use one of the other printStackTrace signatures--one takes a PrintStream arg, one takes a PrintWriter.
Or, when you run it from the command line, you can redirect stderr and stdout. In bourne shell family on Unix it's
java Whatever > /path/to/your/file 2>&1
Or you could use a logging package, such as what's built into Java (since 1.4 I think, maybe 1.3), and configure it to write to a file. or log4j. Personally I like log4j. If you use Jakarta Commons Logging package, you can write the logging calls without regard to which underlying logging system you use.
The last option is the best for any "real" production app, IMHO, but it also involves a bit of a learning curve, and if you've already got printStackTrace() all over your code, it means changing existing code.
¶

Similar Messages

Page Error handling question..

Using APEX 4.1.1.. Hosted instance.. I am testing various error handling functions (Oracle's standard one from documentation and others). I have a page with a standard report, I have defined the page to have an associated error handling function. On the report I have a calculated column that should error out due to a division by 0 error..
Now what I had thought was, the page would handle the error more gracefully than previous version, in that it would show the custom error message I define in the constraints table...
Is there a section of the documentation I am missing that shows at what point the error handling function kicks in and where we need to invoke it otherwise?
Thank you,
Tony Miller
Dallas, TX

Interesting. Had never considered this aspect.
Just did a couple of tests - so it must only come into play from the PL/SQL engine.
Created an sql report:
select floor(dbms_random.value(1,10))/0 num
from dual
connect by level <= 10But the error function never gets hit.
begin
for i in (select floor(dbms_random.value(1,10))/0 num
from dual
connect by level <= 10) loop
htp.p(i.num);
end loop;
end;Function gets hit.
Just looking at the docs, there doesn't appear to be any indication of processing point.
But from Patrick's blog:
This includes errors raised by validation, process, … and all errors raised by the Application Express engine itself.http://www.inside-oracle-apex.com/apex-4-1-error-handling-improvements-part-1/
I guess an SQL report isn't considered as an 'all errors raised by the apex engine'.

Apex 4.1 Error handling question

Apex 4.1
Hi There,
Just had a query regarding error handling. As per Apex documentation we can add more information to our error messages. I wanted to add custom text and also the actual Ora or any other message
E.g
begin
if 1=1 then
    l_error := 1/0;
end if;
exception
when others then
    APEX_ERROR.ADD_ERROR (
    p_message          => 'Error1',
    p_additional_info => 'Test1',
    p_display_location => apex_error.c_inline_in_notification);
end;Wanted to know, if we want to add the actual error message also, what do we need to add to the ADD_ERROR procedure? I wanted to record the sqlerrm message.
Thanks

The only problem with the example was I don't think it handles not null constraints real well. Usually have a constraint name like 'SYS_SOMENUMBER'. So as a result, the extract_constraint_name is not successful.
I handled this by doing the following:
if l_constraint_name IS NULL AND p_error.ora_sqlerrm IS NOT NULL THEN
     --NOT NULL constraints don't display the constraint name in the error, find another way
    --Added check for ora_sqlerrm as if there is a page validation, it still enters the function, but with no sqlerrm
        declare
            l_cons_split APEX_APPLICATION_GLOBAL.VC_ARR2;
            l_owner user_constraints.owner%type;
            l_table_name user_constraints.table_name%type;
            l_column_name user_cons_columns.column_name%type;
            l_table_column varchar2(400);
        BEGIN
            --get the section enclosed in parenthesis
            l_table_column := regexp_substr(p_error.ora_sqlerrm, '$[^)]*$');
            --remove parenthesis and quotes
            l_table_column := regexp_replace(l_table_column, '[(")]');
            --split the data by period
            l_cons_split := apex_util.string_to_table(l_table_column, '.');
            --determine the constraint name by querying user_constraints
            l_table_name := l_cons_split(l_cons_split.COUNT-2);
            l_table_name := l_cons_split(l_cons_split.COUNT-1);
            l_column_name := l_cons_split(l_cons_split.COUNT);
            select uc.constraint_name into l_constraint_name
            from user_constraints uc, user_cons_columns ucc
            where uc.constraint_name = ucc.constraint_name
            and uc.owner = ucc.owner
            and uc.table_name = l_table_name
            and ucc.column_name = l_column_name
            and get_search_condition(uc.constraint_name, uc.owner) like '%IS NOT NULL%'; --gets the search condition as varchar
        END;
    END IF;{code}
That's slightly off topic, but just thought i'd mention it :)

General Labview Error Handler question discussion

Recently two functions were brought to my attention, the General Error Handler and the Simple Error handler.
And I cannot wrap my hand around these two features. While I have been using Labview I have always used the Labview error cluster. When would you use these two features? As I feel the cluster error is much help.
Maybe it is my defnition that I have confused:
The general error handler will display a dialogue box describing the error that will be passed and shuts down the code?
The simple error handler notifys the operator that an error has occured but it can be customized for adding functionality, it takes the error cluster input and determines if an error was generated. "If an error has been generated, the VI displays a dialog box with the error code, a brief description of the error, and the location of the error." How is this not the same as an error cluster?
If anyone has any simple code examples for this or knowledge I greatly appriciate it.
Caleb

Jacobson wrote:
Psireaper9 wrote:
The simple error handler notifys the operator that an error has occured but it can be customized for adding functionality, it takes the error cluster input and determines if an error was generated. "If an error has been generated, the VI displays a dialog box with the error code, a brief description of the error, and the location of the error." How is this not the same as an error cluster?
You are correct that they give the same information. The difference is that if you want to use an error cluster you will need an indicator on your front panel. If you use the simple error handler you won't have to have an error cluster on your front panel but the user will be notified if an error does occur.
Think about all the programs you normally use (excel, chrome, etc.). As a user you expect that errors aren't happening, and if errors do occur then the application will usually just close out and you get an error dialog about the error.
I use the simple error handler with no user interaction to extract the error text. Is there an easier way of doing that?

Fault and Error handling questions

Hi,
I have a few of questions regarding exception handling :
1. Where can I find documentation (i.e. details and when thrown) on all the Standard faults available with BPEL ie. those in
http://schemas.xmlsoap.org/ws/2003/03/business-process/" and
http://schemas.oracle.com/extension
2. Let's say I do not know in advance what specific fault to catch. I add a catchAll inside my scope. When catchAll triggers, I want to get the detail faultmessages of whatever fault caused the catchAll.
3. I want to use a message type from the RuntimeFault.wsdl in my project. Should I copy over the wsdl file to my project folder ? If I do not copy over and import it from it's location (integration/orabpel/system/xmllib), the console is failing runtime when I try to render the input page.
How can I do that ?
Thanks
Arindam

You can find the standard faults from the BPELspec
1.1.
In 10.1.2.0.2 (the latest released version), youcan
use some system xpath functions to extract thefault
information in <catchAll> block:
getFaultAsString( ) returns String
Or
getFaultName( ) returns QName as fault name.Hi Muruga,
Thanks for your reply.
Can you please also let me know :
1. what's the signature of these methods ?
2. I have 10.1.2.0.2 local version. However under
catchall -> assign -> xpath expression builder, I do
not see these 2 functions.
Can you please help.
ThanksHi Muruga,
I tried doing the following :
<faultHandlers>
<catch faultName="bpelx:bindingFault" faultVariable="bindingFaultVar">
<assign name="assignBindingFault">
<copy>
<from expression="concat(bpws:getVariableData('bindingFaultVar','code'),bpws:getVariableData('bindingFaultVar','summary'),bpws:getVariableData('bindingFaultVar','detail'))"/>
<to variable="outputVariable" part="payload" query="/ns1:TransmissionAck/ns1:StackTrace"/>
</copy>
</assign>
</catch>
<catchAll>
<assign name="assignCatchAll">
<copy>
<from expression=""Unexpected Error in the BPEL Process""/>
<to variable="outputVariable" part="payload" query="/ns1:TransmissionAck/ns1:TransmissionText"/>
</copy>
<copy>
<from expression="bpws:getFaultAsString()"/>
<to variable="outputVariable" part="payload" query="/ns1:TransmissionAck/ns1:StackTrace"/>
</copy>
</assign>
</catchAll>
</faultHandlers>
I got the following runtime error when an actual catchAll was caught :
[2006/02/24 17:09:36] "{http://schemas.oracle.com/bpel/extension}remoteFault" has been thrown. less
<remoteFault>
<part name="code" >
<code>17410</code>
</part>
<part name="summary" >
<summary>file:/C:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_WshOtmSyncInboundShipment_19.0.jar/WSH_OTM_INBOUND_GRP.wsdl [ WSH_OTM_INBOUND_GRP_ptt::WSH_OTM_INBOUND_GRP(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'WSH_OTM_INBOUND_GRP' failed due to: Error while converting to a Java array object. Unable to convert the XSD element P_INT_TRIP_INFO whose collection type is WSH_OTM_TRIP_TAB. Cause: java.sql.SQLException: No more data to read from socket ; nested exception is: ORABPEL-11801 Error while converting to a Java array object. Unable to convert the XSD element P_INT_TRIP_INFO whose collection type is WSH_OTM_TRIP_TAB. Cause: java.sql.SQLException: No more data to read from socket Check to ensure that the XML data describing the collection matches the definition of the array in the XSD. Contact oracle support if error is not fixable. </summary>
</part>
<part name="detail" >
<detail>No more data to read from socket</detail>
</part>
</remoteFault>
WS-T Complete
WS-T Close
WS-T Fault
WS-T Cancel
WS-T Compensate
</sequence>
<catchAll>
assignCatchAll (faulted)
[2006/02/24 17:09:36] Updated variable "outputVariable" less
<outputVariable>
<part name="payload" >
<TransmissionAck>
<EchoedTransmissionHeader>
<TransmissionHeader>
<UserName/>
<Password/>
</TransmissionHeader>
</EchoedTransmissionHeader>
<TransmissionAckStatus/>
<TransmissionAckReason/>
<StackTrace/>
<TransmissionText>Unexpected Error in the BPEL Process</TransmissionText>
</TransmissionAck>
</part>
</outputVariable>
[2006/02/24 17:09:37] "XPathException" has been thrown. less
XPath expression failed to execute.
Error while processing xpath expression, the expression is "bpws:getFaultAsString()", the reason is function "bpws:getFaultAsString" not registered.
Please verify the xpath query.
</catchAll>
WS-T Complete
WS-T Close
WS-T Fault
WS-T Cancel
WS-T Compensate
<scope>
WS-T Complete
WS-T Close
WS-T Fault
WS-T Cancel
WS-T Compensate
</sequence>
[2006/02/24 17:09:37] "XPathException" has not been caught by a catch block.
[2006/02/24 17:09:37] BPEL process instance "4503" cancelled
Can you please help.
Thanks

Simple Error Handling Question

I know that in general, when you are handling an error, you can either pass the back by adding a throws declaration to the method in question, or surround with try/catch and handle the error.
What do you do if you want the error to force the application to stop? Just send a simple output message and then stop.
Thx,
hqd

What do you do if you want the error to force the
application to stop? Just send a simple output
message and then stop.You should stop wanting that. If the code in method X
encounters an error it can't deal with, it should
throw that error to whoever calls it. It is the
responsibility of the caller to decide what to do,
not the responsibility of method X.But the buck has to stop somewhere. Are you saying that only the main method should ever stop a program?
Maybe this is one of the gaps in my understanding of good overall design, but it seems perfectly valid to me to have certain methods that, when they error, I know I always want my application to stop. Passing it along up the chain might involve adding a whole bunch of throws declarations.... why... just to say we have no methods that stop the application. Say this piece of code is not longer used in the spot that throws it's possible error up the chain.... now you have to remove all those throws.... isn't this ripple effect on our code bad design?
What am I missing?
Thanks,
hqd

HTTPService error handling question

When i am using HTTPService for Flex-PHP communication i set
HTTPService's 'fault' property which handles error event. So
basically if i have HTTPService set up like this:
<mx:HTTPService id="test" url="
http://localhost/test/test.php"
contentType="application/xml" useProxy="false" method="POST"
fault="httpServiceError(event)">
</mx:HTTPService>
Then 'httpServiceError' method is fired in case of
HTTPService error. What i would like to do in httpServiceError
method is trace the id of the failed HTTPService. I tried with:
public function httpServiceError(evt:FaultEvent):void{
trace(evt.currentTarget.id);
But soon realized that FaultEvent doesn't conatin
'currentTarget' property so this failed. What's the correct way to
find out id of the failed HTTPService?
thanks in advance,
best regards

Which version of flex are you on?
I'm not sure about version 2 but in Flex 3 fault event does
have currentTarget property. What do you get in the trace if you
just say event.currentTarget?
from the docs:
The FAULT event type.
The properties of the event object have the following values:
Property Value
bubbles false
cancelable true, calling preventDefault() from the associated
token's responder.fault method will prevent the service or
operation from dispatching this event
currentTarget The Object that defines the event listener that
handles the event. For example, if you use
myButton.addEventListener() to register an event listener, myButton
is the value of the currentTarget.
fault The Fault object that contains the details of what
caused this event.
message The Message associated with this event.
target The Object that dispatched the event; it is not always
the Object listening for the event. Use the currentTarget property
to always access the Object listening for the event.
token The token that represents the call to the method. Used
in the asynchronous completion token pattern.
ATTA

Global error handling question.

Hello! I've implemented error reporting logic in my app, so when some error occurs the email has been sent with error message, and error id. But it would be nice to locate error place (line number), i know that there is getStackTrace() method of error obj, but it works only if I run app from Flex Builder. How we can implement it in release build app?
Any help would be appreciated.
Thank you.

Moved to the Multiscreen development forum. I don't know of a way to do this but I'm hoping it will get more responses here.
Chris

Question about error-handling in PL/SQL

Hi friends,
I would like to know if there is a way for error handling for insert and update statements in PL/SQL???
Like when for example an insert fails!
thanxx
Schoeib

You should get a book about such fundamentals!
This is not an online course...
begin
insert into emp values(...);
exception
when no_data_found then
when others then
end;

Report and Alert don't executed in the error handler with a JMS proxy service

Hi,
I'm working with OSB 11.1.1.4.0 and I'm facing a problem with the error handler of my JMS proxy service.
My error handler contains two main elements :
- a Report action
- an Alert with a JMS destination defined
When the business service failed the message remain in the queue. It's the expected behavior.
The problem is :
- the report is missing
- the alert is raised but missing in the JMS destination defined in the Alert setting.
I've noticed if I add a Reply with Failure or Success, Report and Alert are successfully executed.
Unfortunately the message don't remain in the JMS queue.
What can I do in order to have my report/alert done and the JMS transaction rollback in order to keep the message in the queue ?
I've already met this problem in the past with alsb v3 and my solution was to add Service Callout in the error handler in order to externalize these actions.
This solution is not convenient and I hope another solution is possible.

Inventorying workgroups can be difficult, especially when it comes to remote access and network security. Because workgroups are not centrally managed, some of the items discussed in this
wiki article on preparing your workgroup environment may require you to visit each machine individually.
For non-domain credentials, you do not use the <systemname>\<user> format, you simply enter the user name. Regarding how to enter the credentials, if you have an account that uses the same username and password on all machines and is an administrator
on all of those machines, then you can enter that in the All computers credentials page of the wizard. You can also do this if they are different user names. However, if some machines have an account with the same user name, such as Administrator,
but different passwords on each machine, you will need to use the Manually enter computer names discovery method, and then enter the information for each group or each machine.
As you can tell, workgroup environments can quickly negate any benefit that the agentless inventory nature of MAP provides.
Please remember to click "Mark as Answer" on the post that helps you, and to click
"Unmark as Answer" if a marked post does not actually answer your question. Please
VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

IDOC to SOAP asynchronous scenario Error handling

Need an expert!!!!!!!!! advise on error handling for IDOC--PI--
SOAP scenario.This is a asynchronous scenario where PI is calling a Legacy system using SOAP adapter.My question is how i can do error handling in this scenario.If i get an alert in pi with payload variable that would be fine, do i need to use BPM and if that is tthe case what will be steps.
Appreciate your help.
Manish

Hello Manish,
My question is how i can do error handling in this scenario.
Use the standard alert framework. Search on SDN / SAP Help for details.
do i need to use BPM and if that is tthe case what will be steps.
BPM is not required to raise alerts, as this is an async call.
Regards,
Neetesh

How to stop execution after generating error message in an error handler?

I am working on ALSB 3.0.I have a proxy consisting of 2 stages in a pipeline pair. I have error handlers for each of the stages. The first stage contains schema validation action. Whenever the schema validation fails,control should transfer to error handler.
The error handler has a publish action and in request action I am calling an xquery transformation to generate error message.Publish action should publish message to a jms based business service configured. My questions are:
1. After getting into the error handler, the first alert msg configured inside request action (of publish action) is generated.Subsequent actions to generate error xml message and to replace the contents of errorXml in $body are not executed.And so no error message is generated or published.
2. I have also configured a reply with failure. Inspite of that,the control shifts to next stage in request pipeline and execution continues.
Can anyone tell me where I need to do the corrections.
Cheers.
Edited by: arrajago on Jun 15, 2009 11:55 PM

Got the answer.Generate error xml outside publish action.Replace action has to placed inside Publish's request action.To stop execution,use Reply action after Publish.

BPM for error handling and acknowledgements

Hi,
Can any one tell me how to handle BPM for error handling and acknowledgements in one scenario.
Please send me the link if you have other wise give me the solution on the same.
Thanks,
Nagesh

Hi !
Just check out these links This might help you.
Usually Application Level Acknowledgement is considered during Sync communication. If you are using RFC, you can make use of Sync communication. So you can handle it without bpm, provided your both sender and receiver are sync interfaces.
To know about Ack-
http://help.sap.com/saphelp_nw2004s/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
you can not dirrectly access the content of the ACK, however the BPM shows different behaviours based on the ACK status. E.g. if the ACK contains a success message the BPM will continue in its normal process, if the ACK contains a permanent error, it will either stop or go through an exception branch (provided such a branch has been defined). Have a look at the documentation: http://help.sap.com/saphelp_nw04/helpdata/en/43/65ce41ae343e2be10000000a1553f6/content.htm It doesnt"t state the above mentioned behaviour in detail but says that you need to define an exception branch.
The trickiest part is always to find out, when you will get a transient vs. as permanent error ack. If you are using ACKs with Proxies refer also to this link http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm and this http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm
The following link has entire configuration of Receiver XI Adapter (including acknowledgements)
http://help.sap.com/saphelp_nw04/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm
 eror handling in BPM.

1. CCMS monitoring
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/42fb24ff-0a01-0010-d48d-ed27a70205a8
2. BPM Monitoring
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
3. Monitoring XML Messages http://help.sap.com/saphelp_nw04/helpdata/en/41/b715045ffc11d5b3ea0050da403d6a/frameset.htm
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
monitoring BPm https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
Reconciliation of Messages in BPM - /people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm
Also see the below BPM related links
check list for BPM https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3bf550d4-0201-0010-b2ae-8569d193124e
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/62/dcef46dae42142911c8f14ca7a7c39/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/de/766840bf0cbf49e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cb/15163ff8519a06e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
Many other examples can be found under the following link at help.sap.com
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
And some weblogs
https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
/people/siva.maranani/blog/2005/05/22/schedule-your-bpm *****
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
/people/michal.krawczyk2/blog/2005/06/11/xi-how-to-retrieve-messageid-from-a-bpm
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
/people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
/people/michal.krawczyk2/blog/2005/09/04/xi-do-you-realy-enjoy-clicking-and-waiting-while-tracing-bpm-steps *****
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements *****
/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
/people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
Also have a look at these seminars,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/daea5871-0701-0010-12aa-c3a0c6d54e02
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/e8515171-0701-0010-be98-e37bec4706cc
Thanks !!!
Regards
Abhishek Agrahari
Questions are welcome here!!
Also mark helpful answers by rewarding points

For IDOC monitoring, analysis and error handling in ALE & idoc

Hello...experts..can u please tell me about idoc monitoring,analysis and error handling..and can u please tell as per interview point of view in this area..if availble can u send material about this...
thx
Message was edited by:
durga kottapalli

Hi,
Reprocessing IDocs with errors
Outbound (BD88)
Once the error has been determined and corrected it is not necessary to resend the IDoc again. You simply resend the IDocs that have already been generated.
Using the IDoc overview screen you need to take note of the following for each IDoc that was not processed:
Error number: 2, 4, 5, 25, 29
Error number: 30 (Execute Check IDoc dispatch to process)
IDoc number
Using the Error number, the IDoc number and the transaction BD88 , with the required message type you can resend the IDoc. Match the error number with this transaction and execute the function for the IDocs incorrectly processed.
Just check the below link, u will get all IDOC related Interview questions
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sappoint.com/abap.html
http://www.sap-img.com/
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://www.sappoint.com/abap.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sap-img.com/
http://www.allsaplinks.com/
Regards,
Suresh.
Message was edited by:
SureshKumar Ramamoorthy

JCo Client Programming and Error Handling

Hi all,
I was wondering if anybody could help me out with some advice on error handling when writing code to send messages to SAP via a JCo Client, particularly IDocs.
I understand from my reading that IDocs are always sent asyncronously to the SAP system from JCo, using JCO.Client.send(). So it is possible (and I have some test code working to do this) to force an exception with say a malformed IDoc, and catch the exception in my code.
But due to the asyncronous nature of the send functionality for IDoc, I cannot see any way of getting back any "business level" exceptions (e.g. Order Number does not exist, Unknown Material, etc.)
So my question is, is it possible to receive any of these type of error messages when sending IDocs to an SAP system using JCo? Perhaps by setting up a JCo Server with the correct error/exception listeners to receive these messages - but are they even sent out in the way?
If not what is the process for handling them?
It is of course possible to look in the SAP system using txn WE02 and see the problem/error but that does not help me to propagate this back to the sending application or to maintain state alignment between the two apps.
Any advice much appreciated!!
Chris

Hi Anil,
you should check on those trheads:
<a href="https://www.sdn.sap.com/irj/sdn/thread?messageID=3104772&#3104772">https://www.sdn.sap.com/irj/sdn/thread?messageID=3104772&#3104772</a>
<a href="https://www.sdn.sap.com/irj/sdn/thread?messageID=579794&#579794">https://www.sdn.sap.com/irj/sdn/thread?messageID=579794&#579794</a>
Regards,
Gianluca Barile

Error Handling Question

Similar Messages

Maybe you are looking for