Catch SAPSQL_INVALID_FIELDNAME error

Hi,
Is it possible to cacht SAPSQL_INVALID_FIELDNAME error ?
When Im trying :
CATCH SYSTEM-EXCEPTIONS SAPSQL_INVALID_FIELDNAME = 1.
ENDCATCH.
I got an error that there is no such exception :/
thx for help

If you are in the release 6.10 or higher, try using TRY... CATCH technique and catch the exceptions of CX_SY_SQL_ERROR class. Here is an example from ABAP Help:
PARAMETERS: column TYPE c LENGTH 8,
            value TYPE c LENGTH 30.
DATA spfli_wa TYPE spfli.
DATA cond_syntax TYPE string.
CONCATENATE column '= value'
            INTO cond_syntax SEPARATED BY space.
TRY.
    SELECT SINGLE *
           FROM spfli
           INTO spfli_wa
           WHERE (cond_syntax).
CATCH cx_sy_dynamic_osql_error.
    MESSAGE `Wrong WHERE condition!` TYPE 'I'.
ENDTRY.

Similar Messages

How can I catch a error in a BAPI?

Hi,
I use BAPI L_TO_CREATE_MULTIPLE. If, for example, I put a warehouse that not is the warehouse of the unit that I want to move, I receive an error that isn't in exceptions.
In the program, I need, in the sy-subrc, catch this error, to do anything.
In this case, the message is L3208.
Thank you very much.

Hello Jose
BAPIs must not raise any exceptions. Why? Because they are intended for external use. However, if you raise an exception during a RFC call the connection will break down. Therefore BAPIs collect the error message in their (usually named) RETURN parameter.
In order to evaluate a BAPI call you can simply code like this:
" Assumption: RETURN parameter is an itab of type BAPIRET2
LOOP AT return TRANSPORTING NO FIELDS
WHERE ( type CA 'AEX' ).
EXIT.
ENDLOOP.
IF ( syst-subrc = 0 ).
" A(bort), E(rror) or X(dump) happened
ENDIF.
Regards
Uwe

Catch the error in to a log file

Hi Team,
Created the script for testing the server online or offline, Could you please tell me how to catch the error in to a file
Try
$Result = Test-Connection -count 1 -computer (Get-Content ServerName.txt) -ErrorAction "Continue"
Catch
   $Result = New-Object PSCustomObject -Property @{
            TimeStamp = Get-Date
            __Server = $env:COMPUTERNAME
            Address = $Computer
            Protocol = ""
            ResponseTime = "Failed"
$Result | Select TimeStamp,__Server,Address,ProtocolAddress,ResponseTime | ft -AutoSize

As mjolinor pointed, you should change the -ErrorAction to Stop to make the control flow into catch block when error occurs. Just change alone is not sufficient because, the control will go to catch block if any of the computer in servername.txt gives error,
and it will not go back to next computer in your text file perform the ping.
So try chaning the code as shown below.
$Outarr = @()
foreach($Comp in (Get-Content C:\temp\servers.txt)) {
Try {
$Result = Test-Connection -count 1 -computer $Comp -ErrorAction stop
Catch {
$Result = New-Object PSCustomObject -Property @{
TimeStamp = Get-Date
__Server = $env:COMPUTERNAME
Address = $Comp
Protocol = ""
ResponseTime = "Failed"
$Outarr +=$Result
$Outarr| Select TimeStamp,__Server,Address,ProtocolAddress,ResponseTime | ft -AutoSize
Hope this helps.
Thanks,
Sitaram Pamarthi
Blog : http://techibee.com
Follow on Twitter
This posting is provided AS IS with no warranties or gurentees,and confers no rights
You can simplify that to:
$Outarr =
foreach($Comp in (Get-Content C:\temp\servers.txt)) {
Try {
Test-Connection -count 1 -computer $Comp -ErrorAction stop
Catch {
[PSCustomObject]@{
TimeStamp = Get-Date
__Server = $env:COMPUTERNAME
Address = $Comp
Protocol = ""
ResponseTime = "Failed"
$Outarr | ft -AutoSize
The [PSCustomObject] type accelerator will take the hash table as a constructor, and coerce it to an [ordered] hash table, so the properties will stay in the same order they were declared. That eliminates the need to use Select-Object afterward to
get them back into the right order.
[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Catch all error information while validating xml content with xsd schema

Hi experts,
I created a java mapping to validating the input xml content with xsd schema (schema validation). What I want is to catch all error message to the xml not just the first error. I used SAXParser in sapxmltoolkit.jar to do the schema validation. The below is a part of my java mapping.
XMLReader parser = XMLReaderFactory.createXMLReader("com.sap.engine.lib.xml.parser.SAXParser");
parser.setFeature( "http://xml.org/sax/features/validation" , true);
parser.setFeature( "http://apache.org/xml/features/validation/schema" , true);
parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaLanguage", "http://www.w3.org/2001/XMLSchema");          parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaSource",this.getClass().getClassLoader().getResourceAsStream(schema)); // schema is my schema name
parser.setErrorHandler(new ParseErrorHandler()); // ParseErrorHandler is my own ErrorHandler which extends DefaultHandler
parser.parse(new InputSource(new ByteArrayInputStream(sinput.getBytes())));
// In error handler, I comment all code so as not to throw any exception
public class ParseErrorHandler extends DefaultHandler
     public void error(SAXParseException e) throws SAXException
          // sSystem.out.println("Error" + e.getMessage());
          // throw e;
     public void fatalError(SAXParseException e)
          // throw e;
          // System.out.println("SAP Fatal Error" + e.getMessage());
Unfortunately the program always stopped while catching the first error. Check the below log.
com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:
ERRORS :
cvc-simple-type : information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' is not valid, because it's value does not satisfy the constraints of facet 'minLength' with value '1'.
cvc-data : information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' is is not valid with respoct to the corresponding simple type definition.
cvc-element : element information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' is associated with invalid data.
cvc-element : element information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]' is not valid with respect to it's complex type definition..
cvc-element : element information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]' is not valid with respect to it's complex type definition..
cvc-element : element information item '/:ShipNotice[1]/:Header[1]/:To[1]' is not valid with respect to it's complex type definition..
cvc-element : element information item '/:ShipNotice[1]/:Header[1]' is not valid with respect to it's complex type definition..
cvc-element : element information item '/:ShipNotice[1]' is not valid with respect to it's complex type definition..
-> com.sap.engine.lib.xml.parser.ParserException:
I tried using Xerces and JAXP to do validation, the same error happened. I have no idea on this. Does xi has its own error handler logic? Is there any body can make me get out of this?
Thanks.

<h6>Hi experts,
<h6>
<h6>I created a java mapping to validating the input xml content with xsd schema (schema validation). What I want is to catch all <h6>error message to the xml not just the first error. I used SAXParser in sapxmltoolkit.jar to do the schema validation. The below <h6>is a part of my java mapping.
<h6>XMLReader parser = XMLReaderFactory.createXMLReader("com.sap.engine.lib.xml.parser.SAXParser");
<h6>parser.setFeature( "http://xml.org/sax/features/validation" , true);
<h6>parser.setFeature( "http://apache.org/xml/features/validation/schema" , true);
<h6>parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaLanguage", "http://www.w3.org/2001/XMLSchema");          <h6>parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaSource",this.getClass().getClassLoader().getResourceAsStream(schema)); <h6>// schema is my schema name
<h6>parser.setErrorHandler(new ParseErrorHandler()); // ParseErrorHandler is my own ErrorHandler which extends Default Handler
<h6>parser.parse(new InputSource(new ByteArrayInputStream(sinput.getBytes())));
<h6>
<h6>// In error handler, I comment all code so as not to throw any exception
<h6>public class ParseErrorHandler extends DefaultHandler
<h6>{
<h6>     public void error(SAXParseException e) throws SAXException
<h6>     {
<h6>          // sSystem.out.println("Error" + e.getMessage());
<h6>          // throw e;
<h6>     }
<h6>
<h6>     public void fatalError(SAXParseException e)
<h6>     {
<h6>          // throw e;
<h6>          // System.out.println("SAP Fatal Error" + e.getMessage());
<h6>
<h6>     }
<h6>
<h6>}
<h6>
<h6>Unfortunately the program always stopped while catching the first error. Check the below log.
<h6>
<h6>com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:
<h6>ERRORS :
<h6>cvc-simple-type : information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' <h6>is not valid, because it's value does not satisfy the constraints of facet 'minLength' with value '1'.
<h6>cvc-data : information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' <h6>is is not valid with respoct to the corresponding simple type definition.
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' <h6>is associated with invalid data.
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]' <h6>is not valid with respect to it's complex type definition..
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]' <h6>is not valid with respect to it's complex type definition..
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]' <h6>is not valid with respect to it's complex type definition..
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]' <h6>is not valid with respect to it's complex type definition..
<h6>cvc-element : element information item '/:ShipNotice[1]' is not valid with <h6>respect to it's complex type definition..
<h6> -> com.sap.engine.lib.xml.parser.ParserException:
<h6>
<h6>
<h6>I tried using Xerces and JAXP to do validation, the same error happened. I have no idea on this. Does xi has its own error <h6>handler logic? Is there any body can make me get out of this?
<h6>Thanks.

How to catch Posting error in File to IDoc Scenario?

I have successfully completed File to IDoc Scenario. Now I am interested in catching posting error. i.e., if mapping goes well and when IDoc is being sent to Recipient system then if any posting error is encountered, then a mail should go to a recipient.
Can anybody suggest the solution.
Regards,
Suraj Kumar

Hi Suraj,
this can be done by triggerring an alert to the recipient.chk out these links to trigger a alert
/people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
/people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
regards
jithesh

Catch Mapping Errors on the Exception Hander in a BPM

Hi All
I am struggling to catch maping error in the Exception Handler, so my question is that, is it possible the catch mapping errors in the Exception Handler using BMP
Thanks
Yonela

Hello Yonela!
In the Transformation Step properties you can specify the exception handler in case the step fail. For more information, please check the help pages below
Events:
http://help.sap.com/saphelp_nw72/helpdata/en/76/9856e633464052a47270ea6c49640a/content.htm
Modeling Exceptions and Exceptions Handling:
http://help.sap.com/saphelp_nw72/helpdata/en/54/bf98c82cd84614a85cfda25d70b175/content.htm
Best regards,
Lucas Santos

How to catch the error occurred in Integration Process, and then save it?

1. how to catch the error occurred in Integration Process, and then save the detailed error message to the file?
2. there are fault message type for inbound message interface, how to use the fault message type in IR?
Thanks,
Michael
Message was edited by: Spring Tang
inital
Message was edited by: Spring Tang
detailed message output
Message was edited by: Spring Tang
fault message type

Hi Spring,
If u give an exception step along with your Transformation Step, whenever some error occurs in your message mapping, this exception block wil be triggered.
You can configure your exception block to do all exception processing that you want. This exception handling is like any other java Exceptio n Handler. You can do anything that you want in your exception handler block on the basis of your requirements.
<i>If an exception is triggered at runtime, the system first searches for the relevant exception handler in surrounding blocks. If it does not find the correct exception handler, it continues the search in the next block in the block hierarchy.
When the system finds the correct system handler, it stops all active steps in the block in which the exception handler is defined and then continues processing in the exception handler branch. Once the exception handler has finished processing, the process is continued after the block.
If the system fails to find an exception handler, it terminates the integration process with an error.</i>
Regards,
Bhavesh

Catching all errors

Hi
is there a way to catch all errors, I know you can do try and
catch fro your code
about how about errors that come from built in Flex component
I am trying to catch all errors and show it to the user in
better format
but most important, it seems flex will be frozen and you can
do anything if the error is not caught and the only way around it
to restart your browser
Please help
Thanks
Kasem

Everything I read suggests that this isn't possible in Flex.
It seems that uncaught exceptions are handled by the Flash player.
This link discusses the problem in Flex 1.5 and it notes the
problem is not fixed in Flex 2.
http://www.mail-archive.com/[email protected]/msg25874.html
I'm going to continue to look. I really can't imagine that
Adobe spent all that time reworking Flex and didn't address this
problem.

Catching an error on a single line

Is there a way to catch an error on a single line in a VBS script? From what I understand the "On Error Resume Next" will apply to all lines in a procedure.
George

Hello George,
unfortunaly there is no way in VBS like the On Error Goto xxx in VB/VBA. You have to encapsulate the crtitcal lines with a On Error Resume Next/On Error Goto 0 pair and find an error with if Err.Number <> 0 then after every line and handle it e.g. with a Exit Sub call.
Matthias
Matthias Alleweldt
Project Engineer / Projektingenieur
Twigeater?

Can I catch the error instead of the DUMP GETWA_NOT_ASSIGNED ???

Hi:
I have the following code:
FIELD-SYMBOLS: . is executed i got a dump GETWA_NOT_ASSIGNED.
Can I catch the error instead of the dump ?
Thank you
Silvia

see the following example to avoid DUMP
PARAMETERS: p_file LIKE rlgrap-filename .
DATA: v_file TYPE string.
DATA: BEGIN OF itab OCCURS 0,
      name(23) TYPE c,
      END OF itab.
DATA: errormessage TYPE char50.
v_file = p_file.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    filename            = v_file
    filetype            = 'ASC'
    has_field_separator = ' '
TABLES
    data_tab            = itab.
RECEIVE RESULTS FROM FUNCTION 'GUI_UPLOAD'
EXCEPTIONS
   file_open_error               = 1
   file_read_error               = 2
   no_batch                      = 3
   gui_refuse_filetransfer       = 4
   invalid_type                  = 5
   no_authority                  = 6
   unknown_error                 = 7
   bad_data_format               = 8
   header_not_allowed            = 9
   separator_not_allowed         = 10
   header_too_long               = 11
   unknown_dp_error              = 12
   access_denied                 = 13
   dp_out_of_memory              = 14
   disk_full                     = 15
   dp_timeout                    = 16
   OTHERS                        = 17 .
break developer.
CASE sy-subrc.
WHEN 0.
    errormessage     = 'Data Loaded'.
WHEN 1.
    errormessage     = 'FILE_OPEN_ERROR'.
WHEN 2.
    errormessage     = 'FILE_READ_ERROR'.
WHEN 3.
    errormessage     = 'NO_BATCH'.
WHEN 4.
    errormessage     = 'GUI_REFUSE_FILETRANSFER'.
WHEN 5.
    errormessage     = 'INVALID_TYPE'.
WHEN 6.
    errormessage     = 'NO_AUTHORITY'.
WHEN 7.
    errormessage     = 'UNKNOWN_ERROR'.
WHEN 8.
    errormessage     = 'BAD_DATA_FORMAT'.
WHEN 9.
    errormessage     = 'HEADER_NOT_ALLOWED'.
WHEN 10.
    errormessage     = 'SEPARATOR_NOT_ALLOWED'.
WHEN 11.
    errormessage     = 'HEADER_TOO_LONG'.
WHEN 12.
    errormessage     = 'UNKNOWN_DP_ERROR'.
WHEN 13.
    errormessage     = 'ACCESS_DENIED'.
WHEN 14.
    errormessage     = 'DP_OUT_OF_MEMORY'.
WHEN 15.
    errormessage     = 'DISK_FULL'.
WHEN 16.
    errormessage     = 'DP_TIMEOUT'.
WHEN 17.
    errormessage     = 'OTHERS'.
ENDCASE.
MESSAGE e000(00) WITH errormessage .

How to catch BCD_OVERFLOW error when passing value to formal parameter?

Hi,
catching runtime error BCD_OVERFLOW exception is simple. However, it's not possible to catch this error directly, if it results from assigning too big value to the formal parameter.
Let's assume simple code with local class lcl_calculator implementing functional method add with two input parameters i_op1 and i_op2 both of type i and result value r_result of type i as well.
The following code dumps, without the exception being caught:
DATA:
   lo_calculator TYPE REF TO lcl_calculator,
   l_result TYPE i.
START-OF-SELECTION.
   TRY.
       CREATE OBJECT lo_calculator.
       l_result = lo_calculator->add(
         i_op1 = 10000000000
         i_op2 = 1 ).
       WRITE:/ l_result.
     CATCH cx_sy_conversion_overflow.
       WRITE:/ 'Error'.
   ENDTRY.
To solve this, the workaround has to be implemented with checking the values being passed to the method before the actual call is made:
DATA:
   lo_calculator TYPE REF TO lcl_calculator,
   l_result TYPE i,
   l_op1 TYPE i,
   l_op2 TYPE i.
START-OF-SELECTION.
   TRY.
       l_op1 = 10000000000.
       l_op2 = 1.
       CREATE OBJECT lo_calculator.
       l_result = lo_calculator->add(
         i_op1 = l_op1
         i_op2 = l_op2 ).
       WRITE:/ l_result.
     CATCH cx_sy_conversion_overflow.
       WRITE:/ 'Error'.
   ENDTRY.
It's the same with the function module call, so it's general unit interface issue. Also, using the exception handling related to the CALL METHOD command does not help here as it's not wrong parameter TYPING which causes the error. It's the VALUE of correctly typed parameter that causes the error.
The CATCH apparently reacts different ways when the assignment is made to the variable and to the formal parameter of the unit. Any idea how to solve the above without using that workaround?
Thank you
Michal

What about using numeric?
CLASS lcl_calculator DEFINITION.
   PUBLIC SECTION.
     METHODS add IMPORTING i_op1 TYPE numeric i_op2 TYPE numeric RETURNING value(r_sum) TYPE i
                  RAISING cx_sy_conversion_overflow.
ENDCLASS.                    "lcl_calculator DEFINITION
CLASS lcl_calculator IMPLEMENTATION.
   METHOD add.
     TRY.
         r_sum = i_op1 + i_op2.
       CATCH cx_sy_arithmetic_overflow.
         RAISE EXCEPTION TYPE cx_sy_conversion_overflow.
     ENDTRY.
   ENDMETHOD.                    "add
ENDCLASS.                    "lcl_calculator IMPLEMENTATION
DATA:
    lo_calculator TYPE REF TO lcl_calculator,
    l_result TYPE i.
START-OF-SELECTION.
   TRY.
       CREATE OBJECT lo_calculator.
       l_result = lo_calculator->add(
         i_op1 = 10000000000
         i_op2 = 1 ).
       WRITE:/ l_result.
     CATCH cx_sy_conversion_overflow.
       WRITE:/ 'Error'.
   ENDTRY.

Catching an error in SUBMIT Statement

Hi,
I am using SUBMIT (REPORT) and RETURN.
How to catch an error when there is one in the REPORT Program that i am calling.

hi
Calling Programs
If you need to program an extensive application, one single program can become very complex. To make the program easier to read, it is often a good idea to divide the required functions among several programs.
As well as using external modularization, in which you store procedures in special non-executable ABAP programs like function groups, you can also call independent programs from within an ABAP program.
The following ABAP statements allow you to start an executable program or transaction. You can either exit the calling program, or have the system return to it when the called program finishes running.
Executable Program
Transaction
Call without return
SUBMIT
LEAVE TO TRANSACTION
Call with return
SUBMIT AND RETURN
CALL TRANSACTION
You can use these statements in any ABAP program. For example, while processing a user action in the output list of an executable program, you might call a transaction whose initial screen is filled with data from the selected list line.
The event LOAD-OF-PROGRAM is triggered each time a program is called. If a corresponding event block is defined in the framework program, it is executed once before the first other processing block is executed.
An interesting remark at this point is that each execution of an executable program actually has a SUBMIT statement as its source. When you enter the program name in a transaction like SE38 or SA38 and choose Execute, a SUBMIT statement occurs in the transaction. Technically speaking, therefore, executable programs have the attribute of being able to be called using SUBMIT, although their principal characteristic from a useru2019s point of view is that they are started in the foreground.
Memory Organization in Program Calls
The first ABAP program in a session on the application server opens its own internal session (roll area) within the main session. All externally-called procedures run in the same internal session as the calling program, that is, the main program and working data of the procedure are loaded into the same memory area in the internal session.
When you call an executable program or a transaction, the system opens a new internal session for each program. Here, there are two possible cases: If the second program does not return control to the calling program when it has finished running, the called program replaces the calling program in the internal session. The contents of the memory of the calling program are deleted. If the second program does return control to the calling program when it has finished running, the session of the called program is not deleted. Instead, it becomes inactive, and its memory contents are placed on a stack. The system can open up to 9 further internal sessions in external program calls.
As well as executable programs and transactions, dialog modules also open a new internal session. Dialog modules were previously used for modularizing screen sequences.
Program Calls and SAP LUWs
An SAP LUW is a logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW. There are various bundling techniques that you can use to ensure that all of the database updates belonging to an SAP LUW are made in the same single database LUW.
Externally-called procedures do not open a new SAP LUW.
However, when you start a new executable program or transaction, a new SAP LUW starts. Database updates belonging to these programs are collected in their own database LUW. If the new program does not return control to the calling program, the SAP LUW of the old program concludes when the new program is called. If, on the other hand, the new program does return control to the calling program, the new SAP LUW runs parallel to the SAP LUW of the calling program.
No new SAP LUW is opened when you call a dialog module. Bundling techniques in a dialog module add the database updates to the database LUW of the calling program. You may sometimes need to call a transaction that runs in the same SAP LUW as the calling program. One technique for doing this is to use the existing transaction as a dialog module. To do this, you need to create a new dialog module with the same main program and initial screen as the transaction. Transactions that are used both as transactions and as dialog modules must be programmed to obey certain rules. For further information, refer to Calling Screen Sequences.
The fact that an external program shares (or does not share) the SAP LUW with its caller has special consequences if the program calls update-task functions or uses COMMIT WORK. For further information, refer to Special LUW Considerations.
syntax:
SUBMIT REPORT01 VIA SELECTION-SCREEN USING SELECTION-SET 'VARIANT1' USING SELECTION-SETS OF PROGRAM 'REPORT00' AND RETURN.

Catching Mapping error at runtime using a udf

Hi AlL,
I read some blog where it was discussed.. we can catch runtime error ? Is it possible?
how will we be able to catch the runtime error say during the mapping we got an error and we want to catch that error and log it somewhere or throw user defined exception?
I guess at runtime all the runtime details are stored in SMPPMAP3 table. which is the field which contain the any runtime error?

Hi,
you cannot do it using an UDF as a uDF will only work on fields that
are in the message
you can throw exceptions from UDF but not catch
to catch you can use an exception branch of a block stpe in an intgration process BPM
Regards,
michal

How to catch the error if an RFC fails due to short dump

Hi All,
I was calling the RFC Function module in parallel processing depends on the number of work processors available. I am getting the return message from the Function module using the perform statement
PERFORMING task_return ON END OF TASK
But I am not able to catch the errors if the RFC has been terminated due to the dump or manually killing the RFC while running.
I need how to handle the RFC if the call has been terminated due to the dump or system failure. Does the RFC return the sy-subrc at this time or can we able to catch the error in any other way.
Thanks & regards,
Vijay

Hello Vijay,
If you're calling RFC from outside SAP using the OCX-SAPFunctions-Library, then you can catch the dump or any other exception occuring in your SAP-Function.
Assuming that, objRFCFunc is the RFC-Function you can get the Excepetion-Code through objRFCFunc.Exception.
It returns a String. If the error was a dump, the String is "SYSTEM_FAILURE". If it is a "regular" Exception you'll get the Exceptioncode. E.g. "NO_DATA_FOUND".
If you need any sample code e.g. VBA-code for use in Office-Applications, let me know.
regards
Sven

How to catch the error code thrown by Oracle client installation?

Hi everyone,
Recently, I'm writing a bat file to install Oracle 11g client for windows, I know the command line should be below, but how to find the error code it return? like the command line I want to run in Windows, the errorlevel will return 0 if the command line is pass, otherwise it will return no-zero:
oui.exe -silent -waitforcompletion -nowait -force -responseFile ...\response\clientruntime.rsp
BTW, I know I can find the error info under the path ...\Oracle\Inventory\logs, but I think it is better if you can tell me another way to catch the error in command line. I just wish that I can determine whether the Oracle provider installation is pass......
Thanks
Lindsay
Edited by: lindsaywang on Oct 6, 2008 1:28 PM

I got it.
Thanks,
TD

Catch SAPSQL_INVALID_FIELDNAME error

Similar Messages

Maybe you are looking for