Raise exception when get ScreenTop of GuiMenu

Hi expert,
When i get ScreenTop property of a GuiMenu object, It raise an exception. Please help me know how can I get GuiMenu ScreenTop and what control i can get this property.
Thanks

Hi Christian,
Not only GuiMemu do no support control location property, there are some controls are the same behavior with GuiMenu control such as Matched code button, Combo Dropdown list, etc. I know the purpose of SAP scripting is support to automatic processing, e-Learning, I'm working on a e-learning system so i need to get control location properties so i can capture control image. Can you tell me SAP Scripting can support some properties as follow in future:
+Can FindByPosition function return the topmost and the leaf control at point, the current FindByPosition function has some problems:
   -Do not return the top most control at point. That is I call this function when the mouse
    point is pointed to menu control, dropdown list, Matched Code button, it return the
    GuiMainWindow.
   -Do not return the "leaf control". that is i call it when the mouse point is pointed to tree
    control, just return the tree control, does not return the tree node. In menu bar
    control, it does not return menu control, just return Menu bar control.
+Can Sap Scripting support control location property to any control that can render on screen.
Best Regards.
Thanh Ngo.
P/S
One more. Can you tell me there is any solution to resolve above problems? thanks a lot.

Similar Messages

Raise exception when the user entered value is not present

Hello Abap experts,
To raise an exception in the function module when the imported variable value is not presnt in the table.
import variable: cust_name.
how to define a exception for this raise it in the code. any examples and suggestions.
Thanks,
BWer

Here is the F1 help on RAISE.

RAISE
Basic form 1
RAISE except.
Effect
This statement is only effective in function modules and methods.
It triggers the exception except.
If the exception is to be handled by the caller of the function module or method ( CALL FUNCTION or CALL METHOD ), the system passes control straight back to the caller. EXPORT parameters of a function module or method are not filled. The EXPORTING, CHANGING, and RETURNING parameters of a function module or method are only filled with the current values if they were defined to be passed by reference. reference).If they are defined to be passed by value, they are not filled.
If the exception is not handled by the caller, the program terminates with an appropriate error message.
Example
Let there be a function module STRING_SPLIT containing the following code (see also the example in the documentation of the CALL FUNCTION statement):
FUNCTION-POOL CSTR.
FUNCTION STRING_SPLIT.
IF STRING NA DELIMITER.
 RAISE NOT_FOUND.
ENDIF.
ENDFUNCTION.
The calling program might then contain the following:
PROGRAM EXAMPLE.
CALL FUNCTION 'STRING_SPLIT'
 EXCEPTIONS
 NOT_FOUND = 7.
IF SY-SUBRC = 7.
WRITE / 'There is a problem.'.
ELSE.
ENDIF.

If the NOT_FOUND exception is raised in a RAISE statement in the function module STRING_SPLIT, the system exits the function module and returns control to the calling program. The return code, which you should evaluate directly after the CALL FUNCTION statement, now contains the value 7.
Note
Runtime errors:
RAISE_EXCEPTION: The caller did not handle the exception that was triggered.
Related
MESSAGE ... RAISING
Additional help
Creating Function Modules

Regards,
Rich Heilman

Raise Exception when Executing Native SQL

Hi ALL,
 when i am executing native sql, it raises following exception:
CX_SY_NATIVE_SQL_ERROR
code as shown below:
REPORT ZABC2.
data:begin of ty_final occurs 0,
vkorg type vbrk-vkorg,
vtweg type vbrk-vtweg,
spart type vbrp-spart,
werks type vbrp-werks,
fkart type vbrk-fkart,
vbeln_invoice type vbrk-vbeln,
matnr type vbrp-matnr,
arktx type vbrp-arktx,
fkimg type vbrp-fkimg,
ntgew type vbrp-ntgew,
mwsbp type vbrp-mwsbp,
posnr type vbrp-posnr,
vbeln type likp-vbeln,
bldat type likp-bldat,
erdat type likp-erdat,
traid type likp-traid,
ernam type likp-ernam,
posnr_do type lips-posnr,
vbeln_so type vbak-vbeln,
audat_so type vbak-audat,
erdat_so type vbak-erdat,
ernam_so type vbak-ernam,
posnr_so type vbap-posnr,
vbeln_contract type vbak-vbeln,
audat_contract type vbak-audat,
erdat_contract type vbak-erdat,
ernam_contract type vbak-ernam,
vbtyp_contract type vbak-vbtyp,
posnr_contract type vbap-posnr,
end of ty_final.
TRY.
break-point.
EXEC SQL .
select
 i1.inv_vkorg,
 i1.inv_vtweg,
 i1.inv_spart,
 i1.inv_werks,
 i1.inv_fkart,
 i1.inv_vbeln,
 i1.inv_matnr,
 i1.inv_arktx,
 i1.inv_fkimg,
 i1.inv_ntgew,
 i1.inv_mwsbp
 i1.inv_posnr,
 d.do_vbeln,
 d.do_bldat,
 d.do_erdat,
 d.do_traid,
 d.do_ernam,
 d.do_posnr,
 s.so_vbeln,
 s.so_audat,
 s.so_erdat,
 s.so_ernam,
 s.so_posnr,
 c.co_vbeln,
 c.co_audat,
 c.co_erdat,
 c.co_ernam,
 c.co_vbtyp,
 c.co_posnr
into :ty_final
from (SELECT
VBAK.VBELN co_vbeln,
VBAK.AUDAT co_audat,
VBAK.ERDAT co_erdat,
VBAK.ERNAM co_ernam,
VBAK.VBTYP co_vbtyp,
VBAP.POSNR CO_POSNR
FROM VBAK , VBAP
WHERE VBAK.VBELN=vbap.vbeln
and vbak.vbtyp='G') c,
(SELECT
vbak.vbeln so_vbeln,
vbak.audat so_audat,
vbak.erdat so_erdat,
vbak.ernam so_ernam,
vbap.posnr so_posnr
FROM VBAK ,VBAP
WHERE vbak.VBELN=vbap.vbeln
and vbak.vbtyp='C') s,
(SELECT
likp.vbeln do_vbeln,
likp.bldat do_bldat,
likp.erdat do_erdat,
likp.traid do_traid,
likp.ernam do_ernam,
lips.posnr do_posnr
FROM LIKP , LIPS
WHERE likp.VBELN=lips.vbeln
and likp.vbtyp='J'.
) d,
(SELECT
vbrk.vkorg inv_vkorg,
vbrk.vtweg inv_vtweg,
vbrp.spart inv_spart,
vbrp.werks inv_werks,
vbrk.fkart inv_fkart,
vbrk.vbeln inv_vbeln,
vbrp.matnr inv_matnr,
vbrp.arktx inv_arktx,
vbrp.fkimg inv_fkimg,
vbrp.ntgew inv_ntgew,
vbrp.mwsbp inv_mwsbp,
vbrp.posnr inv_posnr
FROM VBRK , VBRP
WHERE vbrk.VBELN=vbrp.vbeln
AND vbrk.VBTYP='M'
AND vbrk.FKART NOT IN ('S1','S2','S3')
AND vbrk.FKSTO<>'X') i1,
(SELECT
 vbelv,
 POSNV,
 vbtyp_v,
 vbeln,
 POSNN,
 vbtyp_n
FROM VBFA
where VBTYP_V='G'
AND VBTYP_N='C'
) f1,
(SELECT
 vbelv,
 POSNV,
 vbtyp_v,
 vbeln,
 POSNN,
 vbtyp_n
FROM VBFA
where VBTYP_V='C'
AND VBTYP_N='J'
) f2,
(SELECT
 vbelv,
 POSNV,
 vbtyp_v,
 vbeln,
 POSNN,
 vbtyp_n
FROM VBFA
where VBTYP_V='J'
AND VBTYP_N='M'
) f3
where c.vbeln=f1.vbelv(+)
and f1.vbeln=f2.vbelv(+)
and s.vbeln=f2.vbelv(+)
and f2.vbeln=f3.vbelv(+)
and d.vbeln=f3.vbelv(+)
and i1.vbeln=f3.vbeln(+)
ENDEXEC.
**and c.vbeln=f3.vbelv(+)
**and i1.vbeln=d.vbeln(+)
*if sy-subrc <> 0.
CATCH CX_SY_NATIVE_SQL_ERROR.
ENDTRY.
*ENDIF.
break-point.

Hi,
Try using this ..
data ref1 type ref to CX_SY_NATIVE_SQL_EROR.
try.
exec sql.
endexec.
catch CX_SY_NATIVE_SQL_EROR.
write 'Error ', ref1->SQL_ERROR.
RAISE EXCEPTION myref.
endtry.
Edited by: Vasavi Kotha on Jan 6, 2009 11:26 AM

Back button of internet explorer raise exception when running WAD tamplate

Hi gurus,
when we run a WAD template the users automatically use the back button of the explorer in order to navigate one step backward.
this action raise an exception: "Webpage has expired".
is somebody know a way that could work or a way to eliminate the back button of the explorer?
thanks in advanced
Miri

>> I do not think it is because of the parameters you are entering/using, try without using the
>> parameters (just for testing), if you still get the error then its not the parameters which is causing
>> the problem.
If I create the report without asking for user-entered params, it works.
>> Can you please specify the browser and the tool to display the report you are using? Generally the
>> error popps up when there are any mistakes in html or if you are using a javascript which has a error.
The active browser on the computer is IE7 - 7.0.5730.13
I am using the installed crystal reports 11 program to run the report. I open the report in CR by going to File/Open and selecting the report. Then I get prompted for my ms sql login info, which I enter. Then I see the "Enter Values" window with my data entry fields; but I don't see the nice formatting and buttons which I see when I run this from the other computers; I see only the placeholders. I select or enter data and click on the "OK" link. Then the message box pops up. The message box pops up when I click on any of the links or on the "x" in the upper right. Mesage box is explicit - Intenet Explorer Script Error, etc., as I described in my original post.
Thanks
Azhar

Raise Exception when execute UCMON

Dear all,
I need help. When we execute the transaction UCMON we have a Dump.
Erro tpo.exec.         RAISE_EXCEPTION
Data e hora            31.01.2011 17:44:30
Dump breve ABAP não está complet.gravado (demas.extenso)
TxtBreve
     Exception condition "NOT_FOUND" raised.
O que aconteceu ?
     The current ABAP/4 program encountered an unexpected
     situation.
O que pode ser feito?
     Print out the error message (using the "Print" function)
     and make a note of the actions and input that caused the
     error.
     To resolve the problem, contact your SAP system administrator.
     You can use transaction ST22 (ABAP Dump Analysis) to view and administer
      termination messages, especially those beyond their normal deletion
     date.
     is especially useful if you want to keep a particular message.
Análise do erro
     A RAISE statement in the program "CL_UC_METHOD==================CP" raised the
      exception
     condition "NOT_FOUND".
     Since the exception was not intercepted by a superior program
     in the hierarchy, processing was terminated.
     Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
as p/eliminação de erros
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system you
use the following search criteria:
"RAISE_EXCEPTION" C
"CL_UC_METHOD==================CP" or "CL_UC_METHOD==============
"CREATE_ACCOUNT"
or
"CL_UC_METHOD==================CP" "NOT_FOUND"
or
"UCUWB000 " "NOT_FOUND"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
      after the short dump. In the display, then select the function
      "System->List->Save->Local File (unconverted)".
   3. If the programs are your own programs or modified SAP programs,
      supply the source code.
      To do this, select the Editor function "Further Utilities->
      Upload/Download->Download".
   4. Details regarding the conditions under which the error occurred
      or which actions and input led to the error.
Ambiente de sistema
   SAP Release.............. "640"
   Application server....... "cpsapbwp01"
   Network address.......... "172.16.21.222"
   Operating system......... "Linux"
   Release.................. "2.6.18-238.1.1.el5"
   Hardware type............ "x86_64"
   Character length......... 16 Bits
   Pointer length........... 64 Bits
   Work process number...... 2
   Short dump setting....... "full"
   Database server.......... "bwdb"
   Database type............ "ORACLE"
   Database name............ "BWP"
   Database owner........... "SAPCSB"
   Character set............ "C"
   SAP kernel............... "640"
   Created on............... "May 2 2010 20:07:20"
Created in............... "Linux GNU SLES-10 x86_64 cc4.1.2"
Database version......... "OCI_102 "
Patch level.............. "327"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "Linux 2.6"
Memory usage.............
Roll..................... 16192
EM....................... 29328992
Heap..................... 0
Page..................... 65536
MM Used.................. 23444056
MM Free.................. 1691488
SAP Release.............. "640"
Usuário e transação
    Client.............. 600
    User................ "CS096152"
    Language key........ "P"
    Transaction......... "UCWB_INT "
    Program............. "CL_UC_METHOD==================CP"
    Screen.............. "SAPLUCUM_00 1000"
    Screen line......... 3
Infos p/ponto de cancelamento
    The termination occurred in the ABAP program "CL_UC_METHOD==================CP"
     in "CREATE_ACCOUNT".
    The main program was "UCUWB000 ".
    The termination occurred in line 27 of the source code of the (Include)
     program "CL_UC_METHOD==================CM009"
    of the source code of program "CL_UC_METHOD==================CM009" (when
     calling the editor 270).
Segmento texto fonte
Linha Txt.fonte
    1 * bal080305 090305 826099 pass exception not_found to caller
    2 method CREATE_ACCOUNT .
    3
    4   data:
    5     lo_instance type ref to if_uc_cust_data,
    6     lo_account type ref to cl_uc_account.
    7
    8   clear: eo_account, e_accid.                                 "bal080305
    9
   10   if do_account_factory is initial.
   11     do_account_factory = do_factory->get_account_factory( ).
   12   endif.
   13
   14   if i_accid is initial.
   15     call method do_account_factory->create
   16       exporting io_model    = do_model
   17       importing eo_instance = lo_instance.
   18     call method lo_instance->get_guid
   19       importing e_guid = e_accid.
   20   else.
   21     call method do_account_factory->get_instance_by_guid
   22       exporting io_model    = do_model
   23                 i_guid      = i_accid
   24       importing eo_instance = lo_instance
   25       exceptions not_found = 1.                        "begin bal080305
   26     if not sy-subrc is initial.
>>>>>       raise not_found.
   28     endif.                                                "end bal080305
   29     e_accid = i_accid.
   30   endif.
   31   call method lo_instance->set_ffix( dt_ffix ).
   32
   33   if if_stm_timestamp = gc_true.
   34     lo_account ?= lo_instance.
   35     call method lo_account->set_task_stm_timestamp( gc_true ).
   36   endif.
   37
   38   eo_account ?= lo_instance.
   39
   40 endmethod.   31   call method lo_instance->set_ffix( dt_ffix ).
What happens?
Thanks a lot
Marilia Costa

Hi,
I could recollect same kind of issue in our system. In production system we were facing a short dump. however not in Development and quality.
Is it the same issue with you?
If yes. please check the single selections consistency in development & production.
thanks
Kamal

Bugreport: Long Plugin-Name raises exception when used in item

Hi,
i created an item-type plugin with a rather long name which saves and "compiles" successfully.
Name: Resizeable Textarea (remember Size)
Internal Name: PLUGIN_INFO.ORACLEAPEX.RESIZABLETEXTAREAREMEMBERSIZE
But when i try to use this plugin for an item, following exception is raised:
ORA-20505: Error in DML: p_rowid=6139204663671389, p_alt_rowid=ID, p_rowid2=, p_alt_rowid2=. ORA-12899: value too large for column "APEX_040000"."WWV_FLOW_STEP_ITEMS"."DISPLAY_AS" (actual: 52, maximum: 50)The Problem is caused by the internal name. This should be checked when creating/saving the plugin, or the restriction on DISPLAY_AS needs to be adapted.
thanks for fixing :-)
Peter
Blog: http://www.oracle-and-apex.com
ApexLib: http://apexlib.oracleapex.info
BuilderPlugin: http://builderplugin.oracleapex.info
Work: http://www.click-click.at

Fixed in 4.1
Thanks
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX 4.0 Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Getting TXN timeout exception when getting an XA Oracle Database Connection

Running WLS 8.1 sp5 on Linux in a Cluster (4 servers)
          Using Oracle 10.2.0.2.0 Thin XA driver
          Running Oracle Datbase 9.2.06 or 9.2.07; I think
          I am getting the SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 31 seconds
          It fails at: weblogic.jdbc.jta.DataSource.enlist(Lweblogic/transaction/Transaction;)V(Optimized Method). The exception occurs on all 4 WLS instances at the same time.
          Stack trace at bottom. This problem seems to occur on and off at about the same time. We have not been able to see other jobs that would affect it during this time.
          - Max Pool Size = 25
          - Current and High Connections = 5
          - Num Unavaiable = 0
          - Failure to Reconnect = 0
          - Connection Delay ranges from 57 to 126 milliseconds
          The problem occurs within an MDB. The MDB gets a msg from the JMS queue, fires off an SMTP msg, and tries to update the database and fails due to the timeout on enlisting in the XA transaction.
          Any thoughts on what to look for? Read the info at http://edocs.bea.com/wls/docs81/faq/JTA.html#738205. Is it talking to the Oracle database to enlist. Since occuring on all 4, there is a central place it's failing and I guess the database is a start.
          Thanks. Later...
          - Wayne
          Wed Jan 10 08:30:13 EST 2007: EMS: Exception: EMSSenderDao.mdbChangeMessageQueueStatus() : java.lang.Exception: getMdbDBConnection() : java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 31 seconds
          BEA1-6A0F2B6B5AA26811FBB9
          at weblogic.jdbc.jta.DataSource.enlist(Lweblogic/transaction/Transaction;)V(Optimized Method)
          at weblogic.jdbc.jta.DataSource.getConnection()Ljava/sql/Connection;(Optimized Method)
          at weblogic.jdbc.jta.DataSource.connect(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;(Optimized Method)
          at weblogic.jdbc.common.internal.RmiDataSource.getConnection()Ljava/sql/Connection;(Optimized Method)
          at com.foo_company.ems.dao.EMSSenderDao.mdbChangeMessageQueueStatus(ILjava/lang/String;I)I(Optimized Method)
          at com.foo_company.ems.ejb.emsmessageconsumer.EMSMessageConsumerBean.onMessage(Ljavax/jms/Message;)V(Optimized Method)
          at weblogic.ejb20.internal.MDListener.execute(Lweblogic/kernel/ExecuteThread;)V(Optimized Method)
          at weblogic.ejb20.internal.MDListener.transactionalOnMessage(Ljavax/jms/Message;)V(Optimized Method)
          at weblogic.ejb20.internal.MDListener.onMessage(Ljavax/jms/Message;)V(Optimized Method)
          at weblogic.jms.client.JMSSession.onMessage(Ljavax/jms/MessageListener;Lweblogic/jms/common/MessageImpl;)V(Optimized Method)
          at weblogic.jms.client.JMSSession.execute(Lweblogic/kernel/ExecuteThread;)V(Optimized Method)
          at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)
          at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)
          at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)

Wayne Lau wrote:
          > Running WLS 8.1 sp5 on Linux in a Cluster (4 servers)
          > Using Oracle 10.2.0.2.0 Thin XA driver
          > Running Oracle Datbase 9.2.06 or 9.2.07; I think
          >
          > I am getting the SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 31 seconds
          >
          > It fails at: weblogic.jdbc.jta.DataSource.enlist(Lweblogic/transaction/Transaction;)V(Optimized Method). The exception occurs on all 4 WLS instances at the same time.
          >
          > Stack trace at bottom. This problem seems to occur on and off at about the same time. We have not been able to see other jobs that would affect it during this time.
          > - Max Pool Size = 25
          > - Current and High Connections = 5
          > - Num Unavaiable = 0
          > - Failure to Reconnect = 0
          > - Connection Delay ranges from 57 to 126 milliseconds
          >
          > The problem occurs within an MDB. The MDB gets a msg from the JMS queue, fires off an SMTP msg, and tries to update the database and fails due to the timeout on enlisting in the XA transaction.
          >
          > Any thoughts on what to look for? Read the info at http://edocs.bea.com/wls/docs81/faq/JTA.html#738205. Is it talking to the Oracle database to enlist. Since occuring on all 4, there is a central place it's failing and I guess the database is a start.
          >
          > Thanks. Later...
          >
          >
          > - Wayne
          Hi. At that moment the issue, whatever it is, has already happened.
          Something in the processing of the transaction to this point has
          already taken longer than you have specified that a transaction
          must complete in. Ideally we'd like to see the JTA/JDBC/2PC debug
          logging turned on, so we have lines with timestamps for every
          step in your tx.
          Joe
          > Wed Jan 10 08:30:13 EST 2007: EMS: Exception: EMSSenderDao.mdbChangeMessageQueueStatus() : java.lang.Exception: getMdbDBConnection() : java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 31 seconds
          > BEA1-6A0F2B6B5AA26811FBB9
          > at weblogic.jdbc.jta.DataSource.enlist(Lweblogic/transaction/Transaction;)V(Optimized Method)
          > at weblogic.jdbc.jta.DataSource.getConnection()Ljava/sql/Connection;(Optimized Method)
          > at weblogic.jdbc.jta.DataSource.connect(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;(Optimized Method)
          > at weblogic.jdbc.common.internal.RmiDataSource.getConnection()Ljava/sql/Connection;(Optimized Method)
          > at com.foo_company.ems.dao.EMSSenderDao.mdbChangeMessageQueueStatus(ILjava/lang/String;I)I(Optimized Method)
          > at com.foo_company.ems.ejb.emsmessageconsumer.EMSMessageConsumerBean.onMessage(Ljavax/jms/Message;)V(Optimized Method)
          > at weblogic.ejb20.internal.MDListener.execute(Lweblogic/kernel/ExecuteThread;)V(Optimized Method)
          > at weblogic.ejb20.internal.MDListener.transactionalOnMessage(Ljavax/jms/Message;)V(Optimized Method)
          > at weblogic.ejb20.internal.MDListener.onMessage(Ljavax/jms/Message;)V(Optimized Method)
          > at weblogic.jms.client.JMSSession.onMessage(Ljavax/jms/MessageListener;Lweblogic/jms/common/MessageImpl;)V(Optimized Method)
          > at weblogic.jms.client.JMSSession.execute(Lweblogic/kernel/ExecuteThread;)V(Optimized Method)
          > at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)
          > at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)
          > at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)

Raise exception when call dbms_debug.get_value

create or replace procedure aaa
is
a in integer;
b binary_integer;
c varchar2(200);
begin
a := 1;
b := dbms_debug.get_value('a', 0, c, null);
dbms_output.put_line('return = ' || b);
if b = dbms_debug.error_bogus_frame then
c := 'Frame does not exist';
elsif b = dbms_debug.error_no_debug_info then
c := 'Entrypoint has no debug information';
elsif b = dbms_debug.error_no_such_object then
c := 'variable_name does not exist in frame#';
elsif b = dbms_debug.error_unknown_type then
c := 'The type information in the debug information is illegible';
elsif b = dbms_debug.error_nullvalue then
c := 'Value is NULL';
elsif b = dbms_debug.error_indexed_table then
c := 'The object is a table, but no index was provided';
elsif b = dbms_debug.error_exception then
c := 'exception inside Probe';
end if;
dbms_output.put_line('value = ' || c);
end;
after i call 'execute aaa;', the sqlplusw output
return = 28
value = exception inside Probe
Thanks!

Hi,
I could recollect same kind of issue in our system. In production system we were facing a short dump. however not in Development and quality.
Is it the same issue with you?
If yes. please check the single selections consistency in development & production.
thanks
Kamal

Raise exception while running ad hoc query

Hi,
I receive a "raise exception" when I try to run an existing ad hoc query in the work area: "standard area (client specific)". This does not happen when I when I create a new query or run a existing query in the work area:"Global(cross client)".
How can this be? Very thankful for answers:-)
-hilde

rohit,
just now my client informed that, he is getting same user group, not which he changed from AQB.
Please let me know if there is any other setting....
early reply appreciated..
thanks,
kumar

How can i get the error message from the thrown/raised exception?

DB version:10gR2
Examples for this thread taken from
Want Stored Procs to get exectuted regardless of preceeding SPs Success or
I have a package with several functions and procedures inside.I created a caller procedure called callProcs, which will execute various procedures within the package in the appropriate order.
In the below example i cannot get the error message thrown from line 20
create or replace package body mypackage
is
variable_proc1 number;
variable_proc2 number;
variable_proc3 number;
v_result       number;
my_exception   exception;
procedure proc1
is
begin
select 8/0 into variable_proc1 from dual;
exception
          when others
          then raise my_exception; ----line 20
end;
procedure proc2
is
begin
select 1 into variable_proc2 from dual;
exception
          when others
          then
               null;
end;
procedure proc3
is
begin
select 3 into variable_proc3 from dual;
exception
          when others
          then
               null;
end;
Procedure caller_proc
is
begin
proc1;
proc2;
proc3;
v_result:=variable_proc2+variable_proc3;
dbms_output.put_line('The output is '||v_result);
exception
          when my_exception
          then
dbms_output.put_line('Heyyyyy the error is '||SQLERRM); -- exception caught at line 64 of caller proc
end;
end mypackage;
When i try executing the caller proc, i don't get the error. Instead i get the text User-Defined Exception as shown below
set serveroutput on
exec mypackage.caller_proc;
Heyyyyy the error is User-Defined Exception
PL/SQL procedure successfully completed.Edited by: user10633418 on Mar 10, 2009 11:30 PM

Thank you justin.
Sorry my earlier post was a bit ambiguous.
I wanted the error generated at proc1 to be captured at caller proc's Exception handling section (line 64) so that i could log the error to an ERR_LOG table.
I can actually log this error at proc1 itself like
exception
when others
THEN
error_message :='My custom message for the particular proc '||SQLERRM;
dbms_output.put_line(error_message);
logerror(error_message); --an autonomous error logging proc
raise;But there is a RAISE statement in proc1's exception handling, so the exception gets propogated to caller proc's exception handling section {color:#ff0000}*and another redundant row will be created at ERR_LOG table for the same error because there is a*{color}
logerror(error_message);--an autonomous error logging proc
in the WHEN OTHERS section of exception handling section of the caller proc
I want to avoid the creation of this redundant row in ERR_LOG table.

Catching errors in Web Dynpro for Java when thrown from RFC Raise Exception

Hello Developers,
I'm looking for information that explains how a Web Dynpro for Java application responds and processes errors that are thrown from a Raise Exception event within an RFC.
The Exceptions do not appear to be part of the Model and I can't identify how they get processed.
When rfc HRXSS_CAT_WD_RECORD raises exception PERNR_NOT_LOCKED this exception is passed back to the calling webdynpro CAT DC that displays the exception on the web page along with the log.
I would like to display a friendlier message and without the log. Any information on how to customize the handling of this error would be greatly appreciated.
Thank you,
Terry

[see here|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=%2flibrary%2fuser-interface-technology%2fwdJava%2FHowtoHandleExceptionsEffectivelyWhileWorkingwithWebDynproJava%28WDJ%29.pdf]

He XML message is going over to SRM from XI , but getting an application error (Exception) when checking in sxmb_moni on the SRM side

hi experts ,
we are using classic scenario (ECC 6.6 & SRM 7.0)
we have are configured Procure-to-Pay Scenario ,Note 1263876 - SAP SRM: Configuration of Procure-to-Pay Scenario.
but facing issue.
The XML message is going over to SRM from XI , but getting an application error (Exception) when checking in sxmb_moni on the SRM side. So we are not able to see the PR in the Sourcing cockpit in SRM.
error as below
<SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SRM/SE/Global">ExchangeFaultData</SAP:ApplicationFaultMessage>
<SAP:Stack>Application has thrown an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi Vijay,
Can you tell us the interface name?
If it is stuck in FEH (Application Error) in SRM then you can check the detail error by going into tcode /n/sappo/ppo2.
You need to enter the Business Process, Order Assignment and Mode Of Postprocessing Order and then execute.
It will show you all the messages stuck in application error for that interface and if you double click on any one of them you will get to see the detailed error with options to Discard, Repeat etc.
Let us know if this helps you.
Regards,
Mayur

Getting exception when trying to open Alert Configuration in RW

Hello friends,
I am getting the following exception when i am trying to open the Alert Configuration/Alert Inbox in RWB.
Exception:
com.sap.aii.rwb.exceptions.BuildLandscapeException: No central monitoring server in exchange profile
        at com.sap.aii.rwb.core.MonitoringServer.(MonitoringServer.java:77)
        at com.sap.aii.rwb.agent.server.SLDAgentBean.buildMonitoringServer(SLDAgentBean.java:799)
        at com.sap.aii.rwb.agent.server.SLDAgentBean.getMonitoringServer(SLDAgentBean.java:1462)
        at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0.getMonitoringServer(SLDAgentObjectImpl0.java:999)
        at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getMonitoringServer(SLDAgent_Stub.java:1931)
        at com.sap.aii.rwb.agent.client.EJBAgent.getMonitoringServer(EJBAgent.java:493)
        at jsp_alert_inbox1204719699497._jspService(jsp_alert_inbox1204719699497.java:28)
        at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
        at jsp_FC_Secure1204104271605._jspService(jsp_FC_Secure1204104271605.java:24)
        at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
        at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
        at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Could you please help me out in solving this problem?
Thanks & Regards,
Senthil

From your error, maybe your profile parameter for alert message server is not properly configured:
I just came cross a post elaborating alerting configuration from Aashish Sinha, hope it helps,
Liang
=====Post from Aashish Sinha=======
Prerequisites
The following prerequisites have to be met in order to use the Alert Management (ALM):
· For using the Alert Inbox (BSP based display program of ALM), the corresponding service has to be activated in the service maintenance transaction SICF. Choose Default_host ? sap ? bc ? bsp ? sap ? alert inbox, and Activate in the context menu.
· For customizing or administration of the Alert Management the corresponding authorization role has to be assigned. The end users do not need any additional authorization.
· The central alert server must be maintained as an RFC destination in transaction SM59 in the local system. If there is no suitable user, you have to create a user for the RFC connection in the central alert system in transaction SU01. To make this RFC destination known as the RFC destination of the Alert Management System in the local system, the central alert server must also be selected as the RFC destination in transaction SALRT1 of the local system or in Settings ? RFC-Destination of Alert Server.
If the central alert server is running on the local system in the same client, you do not have to maintain an RFC destination. In this case, you can simply enter NONE in transaction SALRT1.
· If external communication types, such as e-mail, SMS, and fax are used, these communication types must be correctly configured in SAPconnect, because the alerts are then sent from the central alert system via SAPconnect.
Process Flow
The following describes the process flow from alert configuration (transaction ALRTCATDEF) to alert display and confirmation (for example in the alert inbox transaction ALRTINBOX):
1. Optional: You can define alert classifications. These are useful to group alert categories. For example, you can create an alert classification CRM that contains alert categories referring to CRM. Alert classifications can now have subclassifications. This enables you to build up your own classification hierarchy. Especially, if you use the Alert Mangement (ALM) extensively, classification and subclassification help you to organize your ALM alert landscape and to have a clear overview.
2. For different types of alerts you have to define different categories. The category contains various properties and other specifications that define the alerts within that category, for example expiry date, or the escalation recipient. You can define an alert category to suit your business requirements and assign the category to the corresponding classification. For example, for the alert classification CRM you can create the alert categories Contract Cancelled and Decrease in Sales. When the critical situation defined in the alert category arises, the system recognizes this and sends an alert instance of this category to the recipients determined. The alerts can always be found in the display programs configured for the recipient (UWL, application-specific program, or alert inbox). Additionally, the alerts are sent via eventual external communication channels, such as e-mail, sms, or fax.
3. You have to determine recipients so that the Alert Management knows who the recipients of alerts of a particular category are and that the correct parties are informed.
4. You can configure the way how alerts are processed. For the general use of the Alert Management you do not have to change the default settings. However, if for example you want to send alerts to third-party systems, or to be able to confirm alerts by SMS/Internet mail, or to have logs written, then you have to configure alert processing.
5. There is a number of Alert Management administration reports that you must schedule according to your requirements. For example, report RSALERTPROC must be executed in order to enable escalation.
6. Alerts of a particular category must be triggered by an application at runtime. Triggering alerts can be done in various ways. You can call a function module directly or use middleware components that trigger alerts, such as the Business Object Repository (BOR), Post Processing Framework (PPF), SAP Workflow, or CCMS.
7. Recipients can view the alerts assigned to them in the UWL of Enteprise Portal, in application-specific display programs, or in the alert inbox. In addition, alerts can be received as e-mail, SMS, or fax, if these external communication channels are configured in SAPconnect.
8. If the problem causing the alert is solved by a recipient, the recipient can confirm the alert, this means its status is changed and it will not be delivered, escalated, or displayed anymore. Alerts are generally confirmed by the recipient in the display program, such as the UWL or Alert Inbox. However, if an alert is sent by Internet mail or SMS message, it is also possible to confirm it by sending an Internet mail or SMS message back to the SAP system. Alert Management uses inbound processing for this.
Hope this will help you.
Regards
Aashish Sinha
============End of the Post=======================

"Getting exception when trying to run a JDBC code"

Hi,
I am getting this exception when I try to run the Jdbc code. Can some one sort out what is the problem.
Exception in thread "main" java.lang.UnsupportedClassVersionError: TestJdbcGrip
(Unsupported major.minor version 49.0)Regards

The JDBC jarfile you have is either too new, or too old (less liekely) for you current Java version. Download a newer Java version and try that. If it doesn't work, then download the newer version of the JDBC driver and try it with both of the Java versions (both because if it works with both, then you can continue using whichever one you like).

I'm getting "runtime error: unknown exception" when burning DVDs on PE12

I'm getting "runtime error: unknown exception" when burning DVDs on PE12

Some of this may be for Premiere Pro, but SHOULD also help with Premiere Elements
http://helpx.adobe.com/x-productkb/global/troubleshoot-c-runtime-errors-products.html
Also http://www.microsoft.com/en-us/download/details.aspx?id=14632 for a Microsoft download
Also search http://search.microsoft.com/search.aspx?mkt=en-US&setlang=en-US for Microsoft help articles
Set your Premiere Elements DVD output to a folder on your hard drive and then use the FREE Imgburn to burn the folder to disc for DVD... Premiere Elements does NOT burn to a folder for BluRay (send the author a PayPal donation if you like his program)
Read http://forums.adobe.com/thread/1322583 for notes on installing Imgburn WITHOUT any toolbar add-ons... Set Imgburn to use the slowest burn speed your drive and media will use... I set my burn speed to 1x and let Imgburn adjust to the actual minimum

Raise exception when get ScreenTop of GuiMenu

Similar Messages

Maybe you are looking for