Error in HRPAD31 ( Short dump Analysis )

Hi friends,
When i am changing the existing qualification or adding new qualification it is showing this error in short dump
Pls advise me if there is some relationship i am missing in 031 ?
here is the description of short dump
Runtime Error DBIF_RSQL_SQL_ERROR
Exception        CX_SY_OPEN_SQL_DB
Occurred on     10.09.2008 at   10:48:39
An SQL error occurred when accessing a table.
What happened?
What can you do?
Make a note of the actions and input which 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.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', wasneither
caught nor passed along using a RAISING clause, in the procedure"ADATA_DB" "FORM)"
Since the caller of the procedure could not have expected this exception to occcur, the running program was terminated.
The reason for the exception is:
How to correct the error
The exception must either be prevented, caught within the procedure "ADATA_DB"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-01653: unable to extend table SAPR3.HRPAD31 by 80 in tablespace PSAPSTABD"
Internal call code.........: "RSQL/INSR/HRPAD31"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself, use the following search criteria:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"SAPLRHAP" or "LRHAPF1K"
"ADATA_DB"
System environment
SAP Release.............. "620"
Application server....... "Development"
Network address.......... "200.200.200.10"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "2x IA64 Level 3"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "Development"
Database type............ "ORACLE"
Database name............ "VC3"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Aug 16 2007 23:23:39"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "196"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
User, transaction...
Client.............. 600
User................ "HUSER"
Language key........ "E"
Transaction......... "PP01 "
Program............. "SAPLRHAP"
Screen.............. "MP100100 6000"
Screen line......... 16
Information on where terminated
The termination occurred in the ABAP program "SAPLRHAP" in "ADATA_DB".
The main program was "MP100100 ".
The termination occurred in line 57 of the source code of the (Include) program LRHAPF1K"
of the source code of program "LRHAPF1K" (when calling the editor 570).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the procedure "ADATA_DB" "(FORM)" but was not handled locally, not declared in the RAISING clause of the procedure.
The procedure is in the program "SAPLRHAP ". Its source code starts in line 8 of the (Include) program "LRHAPF1K ".
PLS LET ME KNOW IF I NEED TO CHECK ALL MY CONFIGURATION ?

Hi Ted,
It is working, i just logged off and logged in. Now there is no error.
Thanks for all your support. I am struggling on this isse from 3 days and could not sort it out.
I appreciate on more time for your knowledge.
I have rewarded the points also....
Regards
HR user

Similar Messages

What is Short Dump Analysis and secendry index ?

Dear Experts .
1.) What is purpose of T-codes SE30 and ST22 ?
What is Short Dump Analysis ?
2.) What is secendry index , How to use it ? How it effects the Performance of a report ?
Please it is urgent ...
Regards : Rajneesh

Hi
A dump analysis is a comprehensive list that should enable you to identify the causes and possible solutions of program errors. The ABAP Workbench generates a short dump whenever a report or transaction terminates due to a serious error. The system enters the error in the system log and writes a snapshot of the program at the moment when it terminated into a special database table called SNAP.
Dump analyses give the user or programmer information about the causes of the error that has caused the program to terminate. Experienced users can use them to identify very quickly where and why this occurred. He or she can them solve the problem.
The snapshot contains the following information:
Why the program has terminated
What caused the program termination
Where in the program code the termination occurred
What you can do to correct the error
The values of the relevant system fields when the program terminated
The calls or events that were active when the program terminated
Any other programs that are affected.
http://help.sap.com/saphelp_nw70/helpdata/en/c6/617d0ce68c11d2b2ab080009b43351/content.htm
Index: Technical key of a database table.
Primary index: The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
Secondary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.
Structure of an Index
An index can be used to speed up the selection of data records from a table.
An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read.
When creating indexes, please note that:
An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position.
Only those fields whose values significantly restrict the amount of data are meaningful in an index.
When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently changed therefore should not have too many indexes.
Make sure that the indexes on a table are as disjunctive as possible.
(That is they should contain as few fields in common as possible. If two indexes on a table have a large number of common fields, this could make it more difficult for the optimizer to choose the most selective index.)
Accessing tables using Indexes
The database optimizer decides which index on the table should be used by the database to access data records.
You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.
The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.
If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.
When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated

How to troubleshoot runtime error (termination with short dump)

hi all,
i'm new comer on crm. and i got a problem when i accessed tx: segment builder (runtime error: termination with short dump).
i've tried to troubleshoot this problem by set the java2 SDK GUI path on the client side.but it still didn't work.then i tried to activate the automation trace (just perform the procedure which wrote down on error analysis), but i confused when tried to read the trace file and still didn't get the point. FYI, i 'm using sap logon 710 and SAP crm 5.0.
what i've should to do?
should i have to re install my sap logon?
i really need ur assistance!
best regards,
agung

Hi Agung,
Please refer the following SAP Note for your information:
<b>SAP Note: 990263</b>
Best Regards,
Johnny.
Reward with points if it helps.

Empty System Fields after error creates a short dump

Hello!
Could someone please help me?
After calling a function, I catch errors with sy-subrc NE 0.
Handling this error the "normal" way throws a short dump (I marked the row bold), because all the system fields are empty!
Could someone please give me a hint, how to handle this situation?
Many thanx in advance!
Perhaps some code:
CALL FUNCTION 'Z_CONFIRM'
EXPORTING
    is_bdnum      = is_bed-bdnum
TABLES
    et_return     = lt_return
EXCEPTIONS
    error_occured = 1
    lock_error    = 2
OTHERS        = 3.
IF sy-subrc NE 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
I get a short dump with this:
Content of the system fields
Name
Wert
SY-SUBRC
1
SY-INDEX
1
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
HTTP-Steuerung
SY-MSGTY
SY-MSGID
SY-MSGNO
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080117
SY-UZEIT
080907
SY-XPROG
SY-XFORM

Hi,
You need to capture the message like this way
IF sy-subrc eq 1.
   message e999(your mesage class) with 'Error Occured'.
endif.
IF sy-subrc eq 2.
   message e999(your mesage class) with 'Lock error'.
endif.
IF sy-subrc eq 3.
   message e999(your mesage class) with 'Other Errors'.
endif.
a®

Short dump Error-ABAP/4 Run time Error

Hi Expert,
Dump:ABAP/4 Processor:MESSAGE_TYPE_X Why this error came,I would like to Investigation on Perticular error,Please Some body give me an Exact answer,so that i closed the ticket.
Regards,
Raju.

Hi Suresh,
What is the actual issue?
When did you get this error.
To know about this type of error, check below link...
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=dump%3aABAP%2F4Processor%3A+MESSAGE_TYPE_X&adv=false&sortby=cm_rnd_rankvalue
Also check this:
Note 1016317 - SP13:PC: Start type 'Date & time' gets scheduled wrong
"Process chain scheduling results in dump- ABAP/4 processor: MESSAGE_TYPE_X"
Solution:
In the short dump analysis, the process fails at function module
RSS2_PSA_NEW_OLD_DS
call function 'RSDS_DATASOURCE_SINGLE_GET'
Regards,
KK.

Short dump 'Table does not exist in database'

Hello All,
When a report is executing it is going to short dump by saying 'Table does not exist in database'. As per the short dump analysis this issue is happening because of the following   Native SQL statement statement :
Program : %_T050N0 (This is a dynamic program generating by SAP )
Form Name : DYN_LIC_SEL_TOT
exec sql performing LOOP_MOVE_WRITE_ISAP.
select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty into :dcat-lplate, :dcat-matnr,
:dcat-werks, :dcat-charg, :dcat-holdflag,
:dcat-qty from ZLICENSE_R2 where itm_num   = :p_matnr and
                model_lot = :p_charg
endexec.
As per the customer this issue occurring since they migrated the SAP back-end data base from Oralce to DB6. Here I felt that ZLICENSE_R2 is not migrated from the Oracle to DB6. But as per the BASIS Team, even this table was not maintained in Oracle also. If the table was not maintained in the Oracle, this issue should have been there even before migration also.
Following is the short dump details:
Short text
    Table does not exist in database.
What happened?
    The table or view name used does not
    exist in the database.
    The error occurred in the current database connection "DEFAULT".
What can you do?
    Check the spelling of the table names in your report.
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_NATIVE_SQL_ERROR', was not
     caught in
   procedure "DYN_LIC_SEL_TOT" "(FORM)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Triggering SQL statement: "select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty from ZLICENSE_R2 where itm_num = ? and model_lot = ? "
Database error code: "-204"
Could you please let me know what might be the reason for this issue.
Many Thanks in Advance.

Transaction SE11, input ZLICENSE_R2 for table name, and display the table. Did the table display? If not, that is the main problem.
If the table displays, go to menu item Utilities -> Database Object -> Database Utility
In the resulting screen, under the "Status" fields, you should see text "Exists in the database." If you don't, then the table exists in the dictionary, but doesn't exist in the database system. Click the "Create database table" button and then you should be able to run the program.
You may need basis team's help to carryout some of these actions.

Short dump-internal table size issue

Hi,
I get the following message in the short dump analysis for a report.
No storage space available for extending table "IT_920".
You attempted to extend an internal table, but the required space was not available.
Error Analysis:
The internal table "IT_920" could not be enlarged further.
To extend the internal table, 9696 bytes of storage space was
needed, but none was available. At this point, the table "IT_920" has
1008240 entries.
Its an old report and I saw the internal table declaration using the "OCCURS" clause in the internal table declaration.
begin of itab occurs 100.
end of itab.
I tried the option of changing to "OCCURS 0", still issue persists.
Any help would be highly appretiated
CM

Hello CMV,
This is basic problem with SAP internal tables. For every internal table memory is alocated ( Max..256K)...once you cross the memory size/limit of the internal table it resuls in short dump.
Only way to overcome this problem is handle limited number of records at a time..
Please refer following sample code which will help you to avoid short dump while processing large number of records....
SORT TAB_RESULT.
DESCRIBE TABLE TAB_RESULT LINES W_RECORDS.
W_LOW      = 1.
W_UP       = 1000.
*Spliting the records from tab_result1 by pakage of 1000 at a time
*to avoid short dump in case of more records
WHILE W_LOW <= W_RECORDS.
    R_PKUNWE-SIGN = 'I'.
    R_PKUNWE-OPTION = 'EQ'.
    R_WERKS-SIGN = 'I'.
    R_WERKS-OPTION = 'EQ'.
    LOOP AT TAB_RESULT FROM W_LOW TO W_UP.
      MOVE TAB_RESULT-PKUNWE TO R_PKUNWE-LOW.
      MOVE TAB_RESULT-WERKS TO R_WERKS-LOW.
      APPEND R_PKUNWE.
      APPEND R_WERKS.
    ENDLOOP.
*fetch sold to party
     SELECT KUNNR NAME1
       FROM KNA1
       APPENDING CORRESPONDING FIELDS OF TABLE TAB_KNA1
       WHERE KUNNR IN R_PKUNWE.
*fetch plant
SELECT WERKS NAME1
         FROM T001W
         APPENDING CORRESPONDING FIELDS OF TABLE TAB_T001W
         WHERE WERKS IN R_WERKS.
   REFRESH: R_PKUNWE,
            R_WERKS.
    W_LOW = W_LOW + 1000.
    W_UP = W_UP + 1000.
ENDWHILE.
Hope this will help you to solve problem.
Cheers,
Nilesh

Short Dump when the Bex-Report scheduled for Broadcast

Hi Guru's
I am getting the short dump when I am scheduling the Bex-Report for Broadcasting. Need your help to reslove this issue.
Thanks
Navin
Note
The following error text was processed in the system BDV : The current application triggered a termination with a short dump.
The error occurred on the application server spdbwd01_BDV_05 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Form: INTERNAL_ERROR of program SAPLSDCL
Form: PHIO_GET_CONTENT_ACCESS of program SAPLSDCI
Function: SDOK_PHIO_GET_CONTENT_ACCESS of program SAPLSDCI
Function: SKWF_PHIO_CONTENT_ACCESS_GET of program SAPLSKWF_CONTENT
Method: COPY_MIME_TO_FOLDER of program CL_RSRA_KWF_UTILITIES=========CP
Method: GET_STYLESHEET of program CL_RSRA_KWF_TMPL==============CP
Method: CONSTRUCTOR of program CL_RSRA_KWF_TMPL==============CP
Method: SET_TEMPLATE_FOLDER of program CL_RSRA_ENGINE_BC=============CP
Method: CONSTRUCTOR of program CL_RSRA_ENGINE_BC=============CP
Method: EXECUTE_SINGLE of program CL_RSRA_JOB===================CP

HI Navin,
Check the short dump analysis in T-code ST22.
and also check the Information Broadcast Settings / Configuration
Check the error for Emails in t-code SCOT. BASIS Consultants will help you on this issue.
Regards
Daya Sagar

Short Dump: DBIF_RSQL_SQL_ERROR

Hello experts,
I am getting lot of dumps in my BI system (Windows+ Oracle 10.2)
How to correct part is :
Database error text........: "ORA-00600: internal error code,
[20084], [29798105], [7], [29798105], [7], [], [], []"
Internal call code.........: "[RSQL/FTCH/TBTCO ]"
Please check the entries in the system log (Transaction SM21).
And System log is :
Database error 600 requires database administrator to intervene
Database error 600 at FET access to table TBTCO
> ORA-00600: internal error code, arguments: [20084],
> [29798105], [7], [29798105], [7], [], [], []
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081006 160347 NW04SBI7 B7I00 " generated
How will I proceed in this scenario ?
Waiting for your guidance!
Thanks in advance!
Abhilash

And the trace file would be:
ACTION NAME:(55090) 2008-10-07 10:00:59.826
MODULE NAME:(SAPLBTCH                                ) 2008-10-07 10:00:59.826
SERVICE NAME:(SYS$USERS) 2008-10-07 10:00:59.826
SESSION ID:(58.401) 2008-10-07 10:00:59.826
2008-10-07 10:00:59.826
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [20084], [29798105], [7], [29798105], [7], [], [], []
Current SQL statement for this session:
SELECT "JOBNAME" , "JOBCOUNT" , "JOBGROUP" , "INTREPORT" , "STEPCOUNT" , "SDLSTRTDT" , "SDLSTRTTM" , "BTCSYSTEM" , "SDLDATE" , "SDLTIME" , "SDLUNAME" , "LASTCHDATE" , "LASTCHTIME" , "LASTCHNAME" , "RELDATE" , "RELTIME" , "RELUNAME" , "STRTDATE" , "STRTTIME" , "ENDDATE" , "ENDTIME" , "PRDMINS" , "PRDHOURS" , "PRDDAYS" , "PRDWEEKS" , "PRDMONTHS" , "PERIODIC" , "DELANFREP" , "EMERGMODE" , "STATUS" , "NEWFLAG" , "AUTHCKNAM" , "AUTHCKMAN" , "SUCCNUM" , "PREDNUM" , "JOBLOG" , "LASTSTRTDT" , "LASTSTRTTM" , "WPNUMBER" , "WPPROCID" , "EVENTID" , "EVENTPARM" , "BTCSYSREAX" , "JOBCLASS" , "PRIORITY" , "EVENTCOUNT" , "CHECKSTAT" , "CALENDARID" , "PRDBEHAV" , "EXECSERVER" , "EOMCORRECT" , "CALCORRECT" , "REAXSERVER" , "RECLOGSYS" , "RECOBJTYPE" , "RECOBJKEY" , "RECDESCRIB" , "TGTSRVGRP" FROM "TBTCO" WHERE "JOBNAME" LIKE :A0 ESCAPE '#' AND ( "STATUS" = :A1 OR "STATUS" = :A2 ) AND "STRTDATE" >= :A3 AND ( "STRTDATE" < :A4 OR "STRTDATE" = :A5 AND "STRTTIME" <= :A6 )
Call Stack Trace -
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
_ksedst38           CALLrel _ksedst10           0 1
_ksedmp898          CALLrel _ksedst0            0
_ksfdmp14           CALLrel _ksedmp0            3
_kgeriv+146          CALLreg 00000000             B5863A8 3
_kgeasi92           CALLrel _kgeriv0            B5863A8 76720C4 4E74 4
                                                   E80D310
_qerbtRop346        CALLrel _kgeasi0            B5863A8 76720C4 4E74 2 4 0
                                                   1C6AED9 0 0 7 0 0 1C6AED9 0 0
                                                   7 0
_qersoFetch+366      CALLptr 00000000
_qerbtFetch+607      CALL??? 00000000
_kdibr1sf+55         CALL??? 00000000             317EC790 0 0 1 317EC790
                                                   E80D498
_qerbaFndOl125      CALLrel _kdibr1sf0          EBC8198 317EC790 E80D498
                                                   DDC51C4
_qerbaStrmAnd145    CALLrel _qerbaFndOl0
_qerbaFetch121      CALLrel _qerbaStrmAnd0
_kdibr1sf+55         CALL??? 00000000             317EC61C 0 0 1 317EC61C 0
_qerbtFetch1448     CALLrel _kdibr1sf0          ECB3F54 317EC61C 0 ECB3F68
_qertbFetchByRowID+ CALL??? 00000000             317EC464 0 E80D828 1
475
_qeruaFetch+253      CALL??? 00000000
_opifch2+3115        CALL??? 00000000             317EC0FC 1E9B2F4 E80D9D8 18
_opiefn0348         CALLrel _opifch20           89 4 E80DB7C
_opiefn21           CALLrel _opiefn00           4E 4 E80F698 0 0 0 0 0 0 0
_opiodr+1099         CALLreg 00000000             4E 4 E80F698
_ttcpip+1273         CALLreg 00000000             4E 4 E80F698 C9
_opitsk+1017         CALL??? 00000000
_opiino1087         CALLrel _opitsk0            0 0
_opiodr+1099         CALLreg 00000000             3C 4 E80FC30
_opidrv819          CALLrel _opiodr0            3C 4 E80FC30 0
_sou2o45            CALLrel _opidrv0            3C 4 E80FC30
opimaireal112     CALLrel _sou2o0             E80FC24 3C 4 E80FC30
_opimai92           CALLrel opimaireal0       2 E80FC5C
_OracleThreadStart@ CALLrel _opimai+0
4+708
77E64826             CALLreg 00000000
Thanks,
Abhilash

Short dump while running OLI3BW

Hello,
I'm getting a runtime error and a short dump when I try to fill the setup tables for Purchasing.
This is the error mesage:
Error in ABAP application program.
The current ABAP program "SAPLEINS " had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
Function module "MCEX_UPDATE_02" was called
with the parameter "I_EKKO".
This parameter is not defined.
Does anyone have any idea on how to eliminate this error?
Regards,
Sameer

Hi sameer,
try to fill the settings for purchasing application.
1. determine industry sector
2. transaction key maintenance for sap-bw.
execute these settings and try to fill the setup table once again
Regards
Harikrishna N

Caller 70 is missing time out (short dump)

when I was trying to load transaction data into cube , it was failed
the error message was :
short dump : caller 70 is missing
I checked in st22 , it shows that <b>time out</b> .
when check in r/3 side , extraction was over and job was finished.
data is coming upto PSA & is not updating into data target and geting failed after some time.
can any one give me suggestion.
thanks in advance
Ram

Hi Ram.
We were getting the same message. SAP recently published note 631668. It suggests dropping the InfoCube indexes before the load and then rebuilding them afterwards.
I set our system up to do that last night. We didn't get the error last night, but a single set of loads is not enough to make me say that it works. But it might be worth trying in your case.
Regards,
Adam

Short dump (DBIF_RSQL_INVALID_RSQL) during activating ODS

Hello Experts,
I found short dump during activating ODS.
The error message in short dump:
Runtime Error: DBIF_RSQL_INVALID_RSQL
Except.: CX_SY_OPEN_SQL_DB
The termination occurred in the ABAP program "GP7WIVS2MDWGSTMN3ICFDKNAH65" in "ACTIVATE_SIDS".
The main program was "RSODSACT1 ".
I add one InfoObject in the ODS. After activating related objects, I loaded data into the data target.
Data seemed to be loaded correctly, but couldn't be activated.
Any suggestion on this?
-WJ-

Hi,
Please chekc the following SAP Notes you will find solution
Note 908599 - Runtime error SAPSQL_INVALID_FIELDNAME during activation
Note 612995 - P13:ODS:Data activation in bckgrnd always ends 'successfully
Note 1175860 - P19: DSO: SDL: Automatic update after activation
Note 1113603 - P17:DSO:Postprocessing ODS - activating and updating
Note 378447 - Correction: hierarchies do not become green
Note 1272738 - P21:DSO: Activation and automatic updating
Note 794584 - P26:Timestamp field empty in RS2NDPROCPROT after ODSACTIVATE
Note 800086 - P26: ODS activation: Status field in table RS2NDPROCPROT
Note 856292 - P28: Automatic functions: No lock obtained for ERSICENQ
Thanks
Reddy

Custom error message in user exit is giving Short dump

Hi All,
We have a scenario where in if any user try to create/Change/Delete particular types of contract in SAP system we have to issue error message
saying ZIN/ZIR contract creation/Change/Deletion is blocked in SAP. This has to be done from the web application. So we are putting below code
in user exit MV45AFZZ in the form USEREXIT_SAVE_DOCUMENT_PREPARE.
CONSTANTS: lc_vbcpic01 TYPE sy-uname VALUE u2018VBCPIC01u2019, u201CWeb application user ID
         lc_zin           TYPE vbak-auart VALUE u2018ZINu2019,
                     lc_zir            TYPE vbak-auart VALUE u2018ZIRu2019,
                     lc_text(32)    TYPE c VALUE u2018Check long text for more detailsu2019.
DATA: l_uname TYPE sy-uname.
CLEAR: l_uname.
MOVE sy-uname TO l_uname.
*If user ID is not the Web application ID then block the creation/Change/Deletion
IF   l_uname NE lc_vbcpic01
AND ( vbak-auart EQ lc_zin
OR    vbak-auart EQ lc_zir ).
MESSAGE e830(zv) WITH lc_text.
ENDIF.
This code is working fine while creating/Changing the contract i.e. Giving us error message so that user wonu2019t be able to create/change the contract.
But when we delete the contract from VA42, Control is coming to this message statement and is giving Short dump. Below is the error analysis of the dump.
Error Analysis:
During "Exit Command" processing, the program tried to send a " " message.
This is not allowed at this point in processing.
The program had to be terminated.
Screen name.............. "SAPMV45A"
Screen number............ 4001
If any one has come across such scenario/any work around for this problem please let me know your inputs. Your inputs are highly appreciated.
I am working on 4.6C version of SAP.
Note: When i issue information/Warning message contract is getting deleted after displaying the message.
Thanks,
Vinod.

I exactly replicated the same in DELETE_DOCUMENT also
I am getting the Dump. I tried with exit also , but it continued and deleted. To avoid deletion we have to use Leave program or LEAVE TO CURRENT TRANSACTION.
Delete Function is Defined as EXIT command. so it is not possible to give error message. To convice you i just copied demo program and raised the error message.
it is also giving the dump.
copy the demo program DEMO_DYNPRO_AT_EXIT_COMMAND and make this change , information to error .
MODULE cancel INPUT.
MESSAGE e888(sabapdocu) WITH text-001 ok_code input1 input2.
IF ok_code = 'CANCEL'.
    CLEAR ok_code.
    LEAVE PROGRAM.
ENDIF.
ENDMODULE.
and see...

Short dump error report

What is the purpose of short dump error report generated by the system? What r the major parts/section of this report?

hi please look through this:
Whenever any transaction or any process is executed it hits an ABAP code.
If there is any issue in executing the code the situation is called "ABAP DUMP" or 'Short Dump'
Transaction ST22 is used to check any ABAP Dump within a given duration.
U can also fix the issue with the help of ABAP editor (Transaction Code SE38) if u r good with ABAP.
you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
sap-basis sap-basisAll Groups Ignore this text box. It is used to detect spammers.If you enter anything into this text box, no search results will be displayed.
SAP Groups > Technical-functional > sap-basis > Message
About This Group | Invite peers to join this group
<< Prev thread < Prev msg Next msg > Next thread >>
short dump----urgent
Reply from Keith Lewis on 5/2/2003 3:22:00 AM
Good explanation Joy, but it is not only limited to the current day and
yesterday. If you click on the Selection button you can select previous
days as well. In fact you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
Cheers
Keith
SAP R/3 Support Specialist
Information Services International
Tel +44 1664 41 6178 Mobile +44 7887 627818
E-mail email@removed
Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp
Dear sreenivas
If you receive an error message in the R/3 System log (SM21), or if you
see
a terminated update in the update service analysis transaction (SM13), or
DB
realated error ,check for dumps using the dump analysis transaction
(transaction ST22), or choose Tools -> Administration -> Monitoring ->
Dump
analysis.
Transaction ST22 enables you to analyze short dumps from the current and
previous day.
The dump analysis function shows you:
What happened
What you can do
How to correct the error
The dump analysis function also provides an error ID and keywords that you
can use to search in SAPNet, as well as information about:
The system environment
Users and transactions
Transaction ST22 enables you to analyze the following data:
Date, time, user, client
Contents of system and data fields
Contents of internal tables and application tables
ST22 is a very nice feature in SAP. This is where all the system errors
and users mistakes showed up. If there is a problem that you cannot
solve and you contact SAP support, they look at this area to analyze it.
This gives us lead where to handle the problems.
Error analysis
How to correct the error
System environment
User, transaction...
Information on where termination occurred
Contents of system fields
Chosen variables
Active calls / events
Internal notes
Active calls in SAP kernel
List of ABAP programs affected
List of internal tables
Directory of application tables (contents)
Directory of data areas (administration information)
Directory of data areas (contents)
ABAP control blocks CONT
End of runtime analysis
i think this would be helpful
regards
sravani

Short Dump due to TIME_OUT Error

Hi,
We have a situation here, where the monthly data from R/3 is extracted to ODS (Full upload) and subsequently getting uploaded to infocube (Delta). Usually the ODS to infocube updation takes long hours of time (say 8 hours), because of complexity of the update rules over the cube and this was working fine for the past months.
But on 1st of this month when I extracted R/3 data went fine upto ODS, but failed in the further process (i.e., ODS to Infocube) resulting in a short dump. Extract is shown below
Short dump in the Warehouse
Diagnosis
The data update was not completed. A short dump has probably been logged in BW providing information about the error.
System response
"Caller 70" is missing.
Further analysis:
Search in the BW short dump overview for the short dump belonging to the request. Pay attention to the correct time and date on the selection screen.
You get a short dump list using the Wizard or via the menu path "Environment -> Short dump -> In the Data Warehouse".
So I want to try out with another option, Since we know the data coming to ODS on a monthly basis, instead of pushing the data to infocube in delta mode, can I upload the data using full update (but of course weekly wise) to cube ?.
What will be the complications?.
Please guide with your ideas
Thanks in advance,
Arun.

System response
"Caller 70" is missing.
Further analysis:
Search in the BW short dump overview for the short dump belonging to the request. Pay attention to the correct time and date on the selection screen.
You get a short dump list using the Wizard or via the menu path "Environment -> Short dump -> In the Data Warehouse".
Did you follow this recommendation? Did you check the short dump?
If it is really a time_out issue, the short dump will tell you so, but there can also be other causes for caller 70 missing.
It is a time_out you can either increase your time out setting, or decrease the package size in your infopackages;
kr,
Tom

Error in HRPAD31 ( Short dump Analysis )

Similar Messages

Maybe you are looking for