LCA03 generates short dump: DBIF_DSQL2_SQL_ERROR

This dump occurs in procedure "/SAPAPO/OM_SIMSESSION_GET_ALL".
If I look at the logs in LC10, it says:
SIM_SIMSESSION_GET_ALL
Invalid app server: SCX
expected: SCP
We recently completed (or thought we did - seems like we missed a step) a refresh of our sandbox SCM and livecache systems from production.
SCX is the sandbox system and SCP is the production system. This message makes me think that the new sandbox livecache copy is still trying to point to the production SCM system. Has anyone seen this before? Is there something I need to change within the livecache database?
I found a note (877203) that mentions changing the logical system name in /SAPAPO/PRDMAP to the target system, but when I run through the steps to do that, the command: select LOGSYS, count(*) from "SAPR3"."/SAPAPO/PRDMAP" group by logsys returns zero results - thus I didn't think I had to change anything.
I appreciate any feedback.
~TJ

Hello TJ Wilkinson,
-> You are SAP customer. Please create the OSS ticket to the component 'BC-DB-LCA',
     therefore we could logon & take a look closer on the reported issue.
-> Please review the SAP Note No. 1015489 with 'Reason and Prerequisites':
      "You want to access the liveCache from the application server. However, the system name does not match the one specified in the liveCache. This may happen after a homogeneous system copy."
       Did you run the homogeneous system copy?
       What is the version of your system?
       What is the version/build of the liveCache and LCA on the system?
        What LCA/database error reported in the ABAP dump?
Thank you and best regards, Natalia Khlopina

Similar Messages

Short dump while executing the DTP

Dear Experts,
While executing the DTP the system is generated short dump and it is Quality server not in Development system.
The error details are in method Calculate_keyfigure_ds and the data is loaded for IS retails from POSDM.
The error details:
"The MOVE-CORRESPONDING statement can only be used on operands with a
structured type.
In the case at hand, this condition is not fulfilled: Operand "<L_STRUC>" has
the type "C"."
Regards,
Amit

Hi Amit ,
Move corresponding statements can be used for structures only and from the error message it seems that there is datatype mismatch.
Check for the errors ion link :
http://help.sap.com/abapdocu/en/ABAPMOVE-CORRESPONDING.htm
Hope it helps ,
Regards,
Supriya

Short Dump Error DBIF_DSQL2_SQL_ERROR

Hi All,
I am getting a Short dump error DBIF_DSQL2_SQL_ERROR when I try to selectively delete the contents of an infocube. Now, we have a custom program that does this selective deletion. I had no problem when I ran this program in Development system. But when I try to do the same in Testing system, I get a short dump error.
Additional info: We have DB2 for database.
Thanks,
Ashmith Roy

Hi All,
Thanks for your input. The exact error I am getting is in as follows:
Runtime Error          DBIF_DSQL2_SQL_ERROR
Except.                CX_SY_NATIVE_SQL_ERROR
An SQL error occurred when executing Native SQL.
Error "-199" occurred in the current database connection "DEFAULT".
How to correct the error
     Database error text........: "[IBM][CLI Driver][DB2] DSNT408I SQLCODE = -199,
      ERROR: ILLEGAL USE OF KEYWORD FETCH. TOKEN WAS EXPECTED DSNT418I SQLSTATE =
      42601 SQLSTATE RETURN CODE "
     Database error code .......: "-199"
     Triggering SQL statement...: "FETCH NEXT "
     Internal call code.........: "[DBDS/NEW DSQL]"
     Please check the entries in the system log (Transaction SM21).
Information on where terminated
The termination occurred in the ABAP program "GP41YKV36E6C2VFC36AKSJQXCD3" in
      "COUNT".
The termination occurred in line 0 of the source code of the (Include)
program " "
of the source code of program " " (when calling the editor 00).
Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
occurred in the
procedure "COUNT" "(FORM)" but was not handled locally, not declared in the
RAISING clause of the procedure.
The procedure is in the program "GP41YKV36E6C2VFC36AKSJQXCD3 ". Its source code
starts in line 0
of the (Include) program "???".
So could you please advise as to how to correct the error?
Ashmith Roy

Short dump while generating data sources

Hi all,
I've created a source system for MSSQL database. Now, when I'm trying to Generate the Data Source from SQL into BW using 'Select database tables' option in the Source system and execute it for a table (SAMTEST) in the SQL database, the program terminates with a dump as follows.
Error in ABAP application program.
The current ABAP program "RSDL_META_UPLOAD" had to be terminated because one of
the
statements could not be executed.
This is probably due to an error in the ABAP program.
In program "SAPLRSDBC ", the following syntax error occurred
in the Include "LRSDBCO01 " in line 58:
"The field "RSDBC_C_RSADMIN" is unknown, but there are the following fi"
"elds with similar names: "RS_C_RSADMIN" and "RSDRO_C_RSADMINA"."
Author and last person to change the Include are:
Author "SAP "
Last changed by "SAP "                                                -
I think I've missed some custom settings to be done. I'm clueless. Can anyone help in this regard.
Thanks in advance,
Sam

This is a bug in the code. Check oss note 729243 -
"Symptom
The attempt to load data from an external database results in a runtime error with a syntax error in the SAPLRSDBC program.
Other terms
DB Connect, DBC, DBC SYNTAX_ERROR, dump, short dump
Reason and Prerequisites
This is due to a program error.
The LRSDBCO01 include is inconsistent in the corrections of the currency translation for DB Connect in BW 3.5 Support Package 13. This results in the dump with a syntax error in the SAPLRSDBC program.

SAP Short Dumps when generating BSP page

While generating my BSP page a short dump occurs saying that there is too much code basically. (more then 10,000 ABAP statments). This happens on my LAYOUT section of the screen and the weird thing is that I only have 2145 lines of code.
A little background is that we are displaying a tab strip with 8 tabs and many fields on each tab. The user has a few more rules for displaying data but I'm finding that I can't add anymore code. Has anyone found a way around this?

Its not too difficult. From your view that houses the tabstrip container, you just go ahead and call all the controllers for your individual tabs.
<phtmlb:containerTabStrip id                    = "TabStrip3"
                                  collapsed             = "<%= application->T3_COLLAPSED %>"
                                  collapsible           = "TRUE"
                                  firstVisibleItemIndex = "1"
                                  hasContentConnector   = "TRUE"
                                  maxVisibleItems       = "5"
                                  onCollapse            = "myCollapse"
                                  scrollableItems       = "TRUE"
                                  selectedIndex         = "<%= application->SELECTED_chart2 %>" >
          <phtmlb:containerTabStripItem id    = "C1"
                                        title = "<OTR>Hours History</otr>" >
            <phtmlb:containerContentItem>
              <bsp:call url     = "Chart1.do"
                        comp_id = "c1" />
            </phtmlb:containerContentItem>
          </phtmlb:containerTabStripItem>
          <phtmlb:containerTabStripItem id    = "C2"
                                        title = "<OTR>Project Hours Chart</otr>" >
            <phtmlb:containerContentItem>
              <bsp:call url     = "Chart2.do"
                        comp_id = "c2" />
            </phtmlb:containerContentItem>
          </phtmlb:containerTabStripItem>
          <phtmlb:containerTabStripItem id    = "C3"
                                        title = "<OTR>6 week History</otr>" >
            <phtmlb:containerContentItem>
              <bsp:call url     = "Chart3.do"
                        comp_id = "c3" />
            </phtmlb:containerContentItem>
          </phtmlb:containerTabStripItem>
        </phtmlb:containerTabStrip>
I then handle the event for the tabstrip change and put the current selected tab into an application class variable or a model class variable.
****Get a Pointer to the application Object
appl ?= application.
data: event1 type ref to if_htmlb_data.
event1 = cl_htmlb_manager=>get_event_ex( request ).
case event_id.
when 'tabstrip3'.
      if event1->event_type eq cl_phtmlb_containertabstrip=>co_phtmlb_event_tab_selected.
        appl->selected_chart2 = event1->event_server_name.
        clear appl->saved_selected_chart.
      elseif event1->event_type eq cl_phtmlb_containertabstrip=>co_phtmlb_event_collapsed.
        appl->t3_collapsed = 'TRUE'.
      elseif event1->event_type eq cl_phtmlb_containertabstrip=>co_phtmlb_event_expanded.
        appl->t3_collapsed = 'FALSE'.
      endif.
endcase.
Next in each controller at the start start of processing of the controller I just do a check to make sure that I an in the currently selected tab. If not, I perform not controller logic, which in turn doesn't call in application logic from my model class or make a call to any view.
data: appl type ref to zcl_es_bsp_appl_ptime_ent.
appl ?= application.
check appl->selected_chart = 'C1'.
That way all my flow logic (selected tab - active tab) stays in my controller and view doesn't get cluttered up with any of that.

Short Dump generating reports of EWA

Hi Experts,
I get the short dump MESSAGE_TYPE_X when I tried to see the Ewa report?
Any Idea?
Thanks in advance.

Hi,
Mi ST 400 level is 17.
Here is mi dump:
Err.tmpo.ejec.         MESSAGE_TYPE_X
Fecha y hora           10.08.2009 09:37:50
Texto breve
The current application triggered a termination with a short dump.
¿Qué ha sucedido?
The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
Anál.errores
Short text of error message:
    La creación de evento para la sesión EA0000000000881 ha fallado
Long text of error message:
     Diagnóstico
La creación de un evento ha fallado.
     Actividades en el sistema
         La transacción actual se cancela.
     Procedimiento
Procedimiento para la gestión del sistema
         El problema puede estar en el rango de números DSVASEVENT.
         Verifique si el intervalo "01" está creado y si tiene números
         libres. Notifique los resultados de esta exploración a SAP.
Technical information about the message:
    Message class....... "DSVAS"
    Number.............. 093
    Variable 1.......... "EA0000000000881"
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
Posición desencadenante de error tiempo ejecución
    Programa                                SAPLDSVAS_RPGEN
    Include                                 LDSVAS_RPGENU03
    Línea                                   672
    Tp.módulo                               (FUNCTION)
    Nombre módulo                           DSVAS_RPGEN_REPORT_GET_DATA
Detalle código fuente
Lín.      Txt.fte.
642        lf_chapno_old = 0.
643      * Fehlende Kapitelnummern verdichten
644        LOOP AT report_structure.
645          AT NEW chapter.
646            IF lf_chapno_old <> report_structure-chapter.
647              lf_chapno_old = report_structure-chapter.
648              ADD 1 TO lf_chapno.
649            ENDIF.
650          ENDAT.
651          report_structure-chapter = lf_chapno.
652          MODIFY report_structure.
653        ENDLOOP.
654
655
656      * Ereignis "Reportgeneriert" vermerken
657        DATA: ls_dsvassessinstid TYPE dsvassessinstid,
658              lf_event_parameter TYPE dsvasevent-event_parameter.
659      * AH 'SL' wird durch Aufrufer erst spaeter ausgeloest
660        if lf_iCount = 0 or sy-batch is initial.
661          ls_dsvassessinstid-sessitype = sessitype.
662        ls_dsvassessinstid-sessno    = sessno.
663        lf_event_parameter           = ls_dsvassessinstid.
664        CALL FUNCTION 'DSVAS_EVENT_RAISE'
665             EXPORTING
666                  pf_event_type      = 'SL'
667                  pf_event_parameter = lf_event_parameter
668             EXCEPTIONS
669                  failed             = 1
670                  OTHERS             = 2.
671        IF sy-subrc <> 0.
>>>>>          MESSAGE x093(dsvas) WITH ls_dsvassessinstid.
673      *     Ereigniserzeugung für Sitzung &1 fehlgeschlagen
674          ENDIF.
675        endif.
676      * AH
677
678        CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
679             EXPORTING
680                  TEXT = space.
681      ENDFUNCTION.
Thanks in advance!

Short dumps

hI
Can any one explain me the key feautres in analyzing short dumps if we get for any ABAP program.
Thanks.
Venkat.

ABAP Dump Analysis (ST22)
All the data saved in SNAP table. & text messages saved in SNAPT.
ABAP Dumps is the default workspace for the Logs and ABAP Dumps navigator group. The ABAP Dumps workspace provides status information for each mySAP ABAP dump generated for the mySAP managed system that you are monitoring. ABAP Dumps is a predefined workspace that contains the following specific information for each dump:
u2022     Program associated with the dump
u2022     Host computer where the dump originated
u2022     User who created the dump
u2022     Date and time the dump was created
u2022     Names of the instances associated with ABAP dumps
u2022     Summary count of dumps by program
u2022     Summary count of dumps by user
You can use the data for specific dumps for the following purposes:
u2022     Identify the number of ABAP dumps generated for a specific mySAP instance
u2022     Identify runtime problems that are occurring on your system
The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system:
Some common dumps : -
1) COMPUTE_INT_TIMES_OVERFLOW
Whole number overflows on multiplication & addition operation.
Always Declare Result field Larger.
per =    ( act / budget ) * 100.
bal =    it_out1-balance + bal .
pr =     it_out1-t_wtext_pr + pr
2) COMPUTE_BCD_OVERFLOW
A value does not fit in a calculation field.
You may need to define the result field to be larger.
1.     Showu2019s error on internal table. (multiplication & addition)
3) Time out
Reason for error:-
After a certain time, the program terminates to free the work process
for other users who are waiting.
2.     The current setting is 1800 seconds.
3.     Primary Index not Used & Sequencing not proper.
4.     Avoid Nested Loops.
5.     Avoid to use select single in loops
6.     Avoid using INTO CORRESPONDING TO
7.     Avoid using SELECT in loops.
8.     SORT the internal table always and use BINARY SEARCH.
9.     for all entries that time check SY-TFILL.
4)     DBIF_RSQL_INVALID_RSQL
The data read during a SELECT access could not be inserted into the
target field.
Check the Sequence of the select Query field & internal table fields.
5)     DBIF_DSQL2_OBJ_UNKNOWN
Because of Database is not properly connected to Level 2 server.
1)     when ur using set Connection command to connect Level 2 server
That time check the value of Sy-subrc = 0 .
6)     SAPSQL_ARRAY_INSERT_DUPREC
Its show the Error when you are going to insert duplicates record in database using
Insert command.
There are three ways to solve this problem.
1     Delete adjacent duplicate.
ii.     Insert ACCEPTING DUPLICATE KEYS
iii.     modify command
7.     CONVT_NO_NUMBER
Solution:-The program attempted to interpret the value "RTGS " as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
1.     put Input Validation using If Query
2.     when programmer try to pass the Char value to num field
3.     or trying to perform Pack or unpack operation on Char. Fields.
8.      CALL_TRANSACTION_NOT_FOUND
Transaction " " is not listed in the table of transaction codes
The current ABAP/4 program uses CALL TRANSACTION to call the Transaction
& Leave to Transaction
Table TSTC (Transactions) contains no entry for the Transaction " ". This could be due to a program error (incorrect transaction code specified).
Ensure that upper/lower case is correct.
1.     Use capital Values because itu2019s case sensitive.
9)     Table_invalid_index.
When you are going to perform Read Insert, update, Delete operation Using index Value & index value = 0. That time it shows this error.
Check the index value is less then or equal to zero.
10)     DATASET_CANT_OPEN
OPEN DATASET / TRANSFER / CLOSE DATASET
Check Sy-subrc = 0.
11     LIST_TOO_MANY_LPROS
At present, the maximum permitted number of nested screen levels is
restricted to 50.
Set by BASIS.
Use leave to transaction u2018Tcodeu2019 to close all Screens at the end of the program.
12     . DBIF_DSQL2_SQL_ERROR
Because of Database is not properly connected to Level 2 server.
1 when ur using set Connection command to connect Level 2 server
That time check the value of Sy-subrc = 0 .

Report J_1IEWT_CERT getting cancelled, generating ABAP dump!

A long running report J_1IEWT_CERT in background mode is getting cancelled after running for a while and generating the following dump :
Error analysis
    When changing or deleting one or more lines of the internal table
    "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]" or when inserting in the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]", 0 was used as
    the line index. An index less than or equal to zero is not
    allowed.
    The error can occur when using the following options:
    1. "INDEX idx" for specifying the line number in the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]"
       where you want to change, insert or delete.
    2. "FROM idx" for specifying the start index when deleting a line
       area from or inserting a line area into the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
    3. "TO idx" for specifying the end index when deleting a line
       area from or inserting a line area into the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
    At the time of the termination, the table contained 17008 lines.
How to correct the error
    If the error occurred in your own ABAP program or in an SAP
    program you modified, try to remove the error.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "TABLE_INVALID_INDEX" " "
    "J_1IEWT_CERT" or "J_1IEWT_CERT_F01"
    "FILTER_DATA"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
Tried searching for some SAP Notes to fix the issue, no success as of now, Please help me out...

Have you checked these notes ?
363107 Short dump occurs during TDS certificate printing.
803806 Error while genrating TDS certificate 03.01.2005
1066049 J1INCERT - Error while generating TDS certificate
Regards,
Subhash

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 on BAPI_TRANSACTION_COMMIT with destination NONE

Hi All
I am using SAP-PM with Compatible Unit(CU) functionality in ECC6 environment.
After we release the CU design to Generate order we get SHORT DUMP.
Any help will be of great help.
I am pasting the details from the dump file here.
Please let me know.
Appretaite your help.
Thanks
Meghana
Runtime Errors         CALL_FUNCTION_REMOTE_ERROR
Date and Time          27.08.2007 18:01:10
Short text
"The current application triggered a termination with a short dump."
What happened?
Error in the ABAP Application Program
The current ABAP program "/***/SAPLCUORDER_N" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
The error occurred during an RFC call to another system.
In the target system, a short dump has been written as well.
More detailed information on the error cause can be found there.
What can you do?
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 error occurred when executing a REMOTE FUNCTION CALL.
It was logged under the name "MESSAGE_TYPE_X"
on the called page.
How to correct the error
Please refer to the notes described in the
short dump.
System environment
SAP-Release 700
Application server... "MB1ES1005"
Network address...... "10.191.97.206"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 3
Shortdump setting.... "full"
Database server... "MB1ES1005"
Database type..... "ORACLE"
Database name..... "EC6"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jul 25 2007 00:57:05"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 121
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 8176
EM...... 14633136
Heap.... 0
Page.... 131072
MM Used. 5005432
MM Free. 1263944
User and Transaction
Client.............. 200
User................ 10086330
Language key........ "E"
Transaction......... "/***/DESIGN "
Transactions ID..... "409954DC5D77F1C58E2D0013725D3B3B"
Program............. "/***/SAPLCUORDER_N"
Screen.............. "/***/SAPLCUORDER_N 2000"
Screen line......... 34
Information on where terminated
Termination occurred in the ABAP program "/***/SAPLCUORDER_N" - in
"SAVE_DESIGN".
The main program was "/***/SAPLCUORDER_N ".
In the source code you have the termination point in line 594
of the (Include) program "/***/LCUORDER_NF07".
Source Code Extract
Line
SourceCde
564
ENDIF .
565
ENDLOOP .
566
IF l_ret-type = 'E' OR
567
l_ret-type = 'A' .
568
CLEAR: save_okcode .
569
570
Show Messages
571
CALL FUNCTION '/***/N_LOG_ADD_MSG'
572
EXPORTING
573
i_log_type = 'G'
574
TABLES
575
t_ret      = t_ret.
576
PERFORM log_order_create_show .
577
Show first Message
578
     MESSAGE ID l_ret-id TYPE l_ret-type NUMBER l_ret-number
579
     WITH
580
       l_ret-message_v1 l_ret-message_v2
581
       l_ret-message_v3 l_ret-message_v4.
582
CALL FUNCTION '/***/N_DESIGN_INIT' .
583
ELSE .
584
IF g_design_mode = con_mode_crea.
585
Need to update DMS documents with real design number
586
PERFORM document_prepare_002 USING con_desnum_tmp_1
587
lv_desnum.
588
ENDIF.
589
Commit design BAPI's
590
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
591
592
IF save_okcode = con_order.
593
Commit order BAPI's
>>>>>
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
595
DESTINATION 'NONE'.
596
597
call of fct. RFC_CONNECTION_CLOSE is important to get a new
598
initial roll area with initial internal tables next time
599
CALL FUNCTION 'RFC_CONNECTION_CLOSE'
600
EXPORTING
601
destination          = 'NONE'
602
EXCEPTIONS
603
destination_not_open = 1
604
OTHERS               = 2.
605
ENDIF.
606
607
IF lv_desnum IS INITIAL .
608
lv_desnum = /***/cudesign-desnum .
609
ENDIF .
610
SET PARAMETER ID '/***/DESNUM' FIELD lv_desnum .
611
    Changes saved
612
MESSAGE ID '/***/MSG' TYPE 'S' NUMBER '529' WITH lv_desnum .
613
ENDIF .
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
2000
SY-UCOMM
CU01
SY-TITLE
Change Design: 50000109
SY-MSGTY
X
SY-MSGID
00
SY-MSGNO
341
SY-MSGV1
MESSAGE_TYPE_X
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20070827
SY-UZEIT
180110
SY-XPROG
SAPMSSY1
SY-XFORM
XAB_READ
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
4 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF07                    594
SAVE_DESIGN
3 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF07                   2616
CHECK_AND_SAVE_F07
2 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF04                    311
USER_COMMAND_D2000
1 MODULE (PAI) /***/SAPLCUORDER_N                  /***/LCUORDER_NI05                     28
USER_COMMAND_2000
Chosen variables
Name
Val.
No.       4 Ty.          FORM
Name SAVE_DESIGN
%_DUMMY$$
2222
0000
0000
0000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
G_DESIGN_MODE
R
5
2
0
0
CON_MODE_CREA
I
4
9
0
0
GT_NODE_CUI
Table[initial]
SY-REPID
/***/SAPLCUORDER_N
2454254544545445542222222222222222222222
F35DF310C35F2452FE0000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_DESNUM_TMP_1
TM00000001CY
543333333345
4D0000000139
000000000000
000000000000
LV_DESNUM
222222222222
000000000000
000000000000
000000000000
SAVE_OKCODE
CU01
4533222222222222222222222222222222222222222222222222222222222222222222
3501000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
CON_ORDER
CU01
4533222222222222222222222222222222222222222222222222222222222222222222
3501000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
SY-XPROG
SAPMSSY1
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_DELETE
LVMS
4545222222222222222222222222222222222222222222222222222222222222222222
C6D3000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
No.       3 Ty.          FORM
Name CHECK_AND_SAVE_F07
CL_GUI_ALV_GRID=>MC_MB_VIEW
&MB_VIEW
2445544522222222222222222222222222222222222222222222222222222222222222
6D2F695700000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
GT_OP
Table IT_303[2x1320]
PROGRAM=/***/SAPLCUORDER_NDATA=GT_OP
Table reference: 118
TABH+ 0(20) = 7039FC3C5824DB3C00000000760000002F010000
TABH+ 20(20) = 0200000028050000FFFFFFFF0400000030140000
TABH+ 40( 8) = 08000000C1308001
store        = 0x7039FC3C
ext1         = 0x5824DB3C
shmId        = 0     (0x00000000)
id           = 118   (0x76000000)
label        = 303   (0x2F010000)
fill         = 2     (0x02000000)
leng         = 1320 (0x28050000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000093
occu         = 8     (0x08000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x2010FC3C
pgHook       = 0x00000000
idxPtr       = 0x00000000
shmTabhSet   = 0x00000000
id           = 234   (0xEA000000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 8     (0x08000000)
lineAlloc    = 8     (0x08000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x60B7153D
collHook     = 0x00000000
ext2         = 0x1024DB3C
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xE00FFC3C
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
G_BADI_PROGRAM
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LOG_ERROR
2
0
0
0
CON_BUTT_DELETED
@11QDelete@
43355466676422222222222222222222222222222222
011C145C545000000000000000000000000000000000
00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000
G_CU_EXIT_CU_EXPLODE
F0000000
F0000000
/***/CUDESIGN-OBJNR
CY00000000000000008835
4533333333333333333333
3900000000000000008835
0000000000000000000000
0000000000000000000000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
G_SEC_COUNT
0
0000
0000
LV_UPD
X
5
8
0
0
%_SPACE
2
0
0
0
GS_ROW_NO
0.0.0.1.
0000
1000
0000
0000
SCREEN
/***/CUDESIGN-GLTRP
2454245445444244555222222222222222222222222222222222222222222222222222222222222222222222222222
F35DF3545397ED7C420000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-MSGID
00
33222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
SWO_%CONTAINER
000000000
2222222222222222222222222222222233333333322222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
0
0
SY-MSGNO
341
333
341
000
000
/***/CVCUI-CUTYP
2
0
0
0
SY-MSGV1
MESSAGE_TYPE_X
44554445555455222222222222222222222222222222222222
D533175F4905F8000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
No.       2 Ty.          FORM
Name USER_COMMAND_D2000
/***/CVCUI
0.0.0.0.0.0.0.1.                                                                         000000
2220000000022222222222222222222222222222222222222222222222222222222222222222222222223333332222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
/***/SAPLCUORDER_N
2454254544545445542222222222222222222222
F35DF310C35F2452FE0000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_MODE_COPY
C
4
3
0
0
LT_BAPI_RETURN
Table IT_1778[2x1088]
PROGRAM=/***/SAPLCUORDER_NFORM=USER_COMMAND_D2000DATA=LT_BAPI_RETURN
Table reference: 310
TABH+ 0(20) = 8837083D407E1C3D0000000036010000F2060000
TABH+ 20(20) = 0200000040040000FFFFFFFF04000000F0170000
TABH+ 40( 8) = 08000000C1308101
store        = 0x8837083D
ext1         = 0x407E1C3D
shmId        = 0     (0x00000000)
id           = 310   (0x36010000)
label        = 1778 (0xF2060000)
fill         = 2     (0x02000000)
leng         = 1088 (0x40040000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000113
occu         = 8     (0x08000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
groupCntl    = 0
rfc          = 1
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x50C6073D
pgHook       = 0x00000000
idxPtr       = 0x00000000
shmTabhSet   = 0x00000000
id           = 1534 (0xFE050000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 8     (0x08000000)
lineAlloc    = 8     (0x08000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x00000000
collHook     = 0x00000000
ext2         = 0x6067033D
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xE82F063D
delta_head   = 0000000000000000CF000000000000000400000020180000000000004D00430055004F000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
CON_MODE_ORDE
O
4
F
0
0
TGSBT
22222222222222222222222222222222222222
00000000000000000000000000000000000000
00000000000000000000000000000000000000
00000000000000000000000000000000000000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
LS_NUMBERS-AUFNR_NEW
000001000677
333333333333
000001000677
000000000000
000000000000
T024I
200UT10100PG for Term & Comp
33355333335426672567622246672222222222222222
20054101000706F20452D0603FD00000000000000000
00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000
LS_T399X
200UT10UM01                  X    INST 30UT01UT01
3335533543322222222222222222252222445522335533553322222222222222222222222222222222222222222222
20054105D01000000000000000000800009E3400305401540100000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
CON_VBKZ_U
U
5
5
0
0
/***/CU_ORDER_IO-DISP_FACTOR
2097152
0
0
LS_DESIGN
200########000050000109DDCY00000000000000008835PROFILE1 0001UT10UM0100220100MWH001
333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
/***/CUDESIGN
200########000050000109DDCY00000000000000008835PROFILE1 0001UT10UM0100220100MWH001
333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_DROP_COUNT
0
0000
0000
LS_DESIGN-DESNUM
000050000109
333333333333
000050000109
000000000000
000000000000
No.       1 Ty.          MODULE (PAI)
Name USER_COMMAND_2000
GT_SELTAB_INIT
Table[initial]
Internal notes
The termination was triggered in function "RfcExtendedReceive"
of the SAP kernel, in line 422 of the module
"//bas/700_REL/src/krn/rfc/abrfcrcv.c#4".
The internal operation just processed is "FUNC".
Internal mode was started at 20070827180011.
Status of connection:
RFC state: " "
RFC error text: "RFC_ERROR_SYSTEM_FAILURE"
CPI-C error text: "The current application triggered a termination with a short
dump."
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App       : disp+work.EXE (pid=26488)
When      : 8/27/2007 18:1:10.942
Threads   : 2
Computer Name       : MB1ES1005
User Name           : ec6adm
Number of Processors: 2
Processor Type: x86 Family 15 Model 4 Stepping 10
Windows Version     : 5.2 Current Build: 3790
State Dump for Thread Id 5e10
eax=000f93c0 ebx=0000042c ecx=00003118 edx=00000000 esi=0000042c edi=00000000
eip=7c82ed54 esp=056d71f0 ebp=056d7260 iopl=0         nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000             efl=00200297
function : KiFastSystemCallRet
7c82ed54 c3               ret
7c82ed55 8da42400000000   lea     esp,[esp]              ss:056d71f0=7c822124
7c82ed5c 8d642400         lea     esp,[esp]              ss:62bd5803=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
056d7260 77e6ba42 0000042c 0001d4c0 00000000 056d7298 ntdll!KiFastSystemCallRet
056d7274 0109504d 0000042c 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
056d7298 00582118 00582151 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess (ntstcdbg.c (501))
056d729c 00582151 7c38b5c8 7c38b5c8 7c38b5c8 01e9b1b8 disp+work!NTStack (dptstack.c (1367))
056d72b8 00582185 7c38b5c8 00000000 008b7ec8 7c38b5c8 disp+work!CTrcStack2 (dptstack.c (352))
056d72c4 008b7ec8 7c38b5c8 00000000 005f0059 00330030 disp+work!CTrcStack (dptstack.c (182))
056d72e8 008bb39f 00711076 056d8018 056d7be8 00200020 disp+work!rabax_CStackSave [abrabax.c (7063)
056d7b90 009eca8b 020b9e4c 020b9e14 000001a6 5d88acf0 disp+work!ab_rabax (abrabax.c (1243))
056d7bcc 009ed19e 00000003 00711076 00000020 00000000 disp+work!rcv_message (abrfcrcv.c (422))
056d8068 009ed29d 00000003 00000000 00710c47 056d80c0 disp+work!RfcExtendedReceive [abrfcrcv.c (14
056d808c 00714873 00000003 00710c47 056d80c0 00711076 disp+work!ab_rfcreceive (abrfcrcv.c (59))
056d80e4 0071886b 2694a7c8 2694a7cc 2694a7cc 2694a7cc disp+work!jfunc_get (abfunc.c (5103))
056d89f4 007191d0 00000003 000000b4 00000000 05e8b7c0 disp+work!jfunc_nonstandard [abfunc.c (1655)
056dcfb0 006e3e2d 00000003 3ced8f90 00000000 056dd018 disp+work!ab_jfunc (abfunc.c (554))
056dd018 0081cb5e 00000000 3ced8f90 056dd164 3cedb514 disp+work!ab_extri (abextri.c (552))
056dd02c 00897dbd 00000000 3cedae46 005bf4cd 3ceda13c disp+work!ab_xevent (abrunt1.c (281))
056dd038 005bf4cd 3ceda13c 000000ea 3cedae46 00000000 disp+work!ab_dstep (abdynpro.c (492))
056dd164 005c25be 3ced8f90 3ced8f90 056dfc78 00000000 disp+work!dynpmcal (dymainstp.c (2398))
056dd178 005c1def 00000001 3ced8f90 00000003 056dfc78 disp+work!dynppai0 (dymainstp.c (1004))
056dd194 00595e69 3ced8f90 00000001 00000001 00000001 disp+work!dynprctl (dymainstp.c (360))
056dfcec 00490e06 00000004 0049d15f 00000004 01dadd00 disp+work!dynpen00 (dymain.c (1628))
056dfcf4 0049d15f 00000004 01dadd00 00000003 00000002 disp+work!Thdynpen00 (thxxhead.c (4773))
056dfee0 0049d6d6 00000001 00000000 00000000 00430000 disp+work!TskhLoop (thxxhead.c (4455))
056dff00 00421c36 00000000 00000000 7ffde000 056dff60 disp+work!ThStart (thxxhead.c (1173))
056dff14 00401080 00000003 05876980 00000001 00000000 disp+work!DpMain (dpxxdisp.c (1121))
056dff60 01242970 00000003 05876980 05877a10 01cce000 disp+work!nlsui_main (thxxanf.c (82))
056dffc0 77e523e5 00000000 00000000 7ffde000 8967f020 disp+work!wmainCRTStartup (crtexe.c (395))
056dfff0 00000000 0124282d 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
State Dump for Thread Id 61fc
eax=00000000 ebx=00000103 ecx=0587a700 edx=02714360 esi=00000000 edi=00000000
eip=7c82ed54 esp=0799fec0 ebp=0799ff04 iopl=0         nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000             efl=00000246
function : KiFastSystemCallRet
7c82ed54 c3               ret
7c82ed55 8da42400000000   lea     esp,[esp]              ss:0799fec0=7c821514
7c82ed5c 8d642400         lea     esp,[esp]              ss:64e9e4d3=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0799ff04 0119030a 000006e0 00000000 00000000 0587a798 ntdll!KiFastSystemCallRet
0799ff84 7c349565 00000000 00000000 00000000 0587a700 disp+work!SigIMsgFunc (signt.c (610))
0799ffb8 77e6608b 0587a700 00000000 00000000 0587a700 MSVCR71!endthreadex
0799ffec 00000000 7c3494f6 0587a700 00000000 00000000 kernel32!GetModuleFileNameA
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
/***/SAPLCUORDER_N
0
10.08.2007
10:12:44
541696
E
1
Typ
/***/CUDESIGN
0
10.08.2007
10:05:19
7168
2
Typ
/***/CU_ORDER_IO
0
10.08.2007
09:53:38
4096
3
Typ
/***/DESTYPE
0
10.08.2007
10:05:21
2048
4
Typ
/***/PRF_ORD
0
10.08.2007
10:05:21
4096
5
Prg
SAPMSSYD
0
04.04.2007
10:28:36
21504
E
6
Prg
SAPFSYSCALLS
0
09.09.2004
14:18:32
8192
E
7
Typ
/***/G_CUST
0
10.08.2007
09:53:39
3072
8
Prg
/***/SAPLTABLES
8
10.08.2007
10:13:00
19456
E
9
Typ
/***/G_CHAR
0
10.08.2007
10:05:21
3072
10
Prg
SAPLCTCE
10
09.09.2004
14:18:34
9216
E
11
Typ
CABN
0
18.09.2001
10:02:26
12288
12
Prg
SAPLICON
12
04.04.2007
10:10:28
27648
E
13
Prg
%_CICON
12
07.02.2006
10:40:00
104448
E
14
Typ
ICONT
0
04.04.2007
10:10:08
2048
15
Typ
NRIV
0
02.04.1998
08:14:54
3072
16
Prg
SAPLBSVA
16
04.04.2007
14:47:00
296960
E
17
Typ
/***/CU_ORDER_S_OP_N
0
10.08.2007
09:53:39
14336
18
Prg
CL_GUI_CONTROL================CP
18
28.02.2005
21:03:09
112640
E
19
Prg
%_CCNTL
18
18.02.2005
14:15:08
15360
E
20
Typ
OBJ_RECORD
0
14.02.1998
08:30:43
2048
21
Prg
CL_GUI_OBJECT=================CP
21
05.07.2005
13:10:15
375808
E
22
Prg
CL_GUI_CFW====================CP
22
28.02.2005
21:03:09
172032
E
23
Prg
CL_GUI_PROPS_CONSUMER=========CP
23
18.02.2005
14:15:08
30720
E
24
Prg
SAPLTHFB
24
04.04.2007
13:24:38
390144
E
25
Typ
EUDB
0
06.11.2003
20:28:08
8192
26
Prg
SAPLSFES
26
08.08.2007
16:46:17
259072
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Prg
SAPLSTTM

Yes even i find it strange. But there is no syntax error and the fact is that it was working 2 days back. Suddenly it has started giving us this dump.
The code is as follows.
Commit design BAPI's
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
      IF save_okcode = con_order.
Commit order BAPI's
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          DESTINATION 'NONE'.
Here con_order is CU01.
Please let me know if anybody has faced this problem earlier.
Thanks in Advance
Meghana

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

Short dump in VF01 - Syntax error in program "RKEAK9RECP3000001"

Helo all,
We recently copied our production client to a QA client and when we try to save an SD invoice (VF01), we get a short dump titled - Syntax error in program "RKEAK9RECP3000001".
The dump long text states:
"The Dictionary structure or table "K9RECP3000001" is either not active"
" or does not exist."
and
NOTE in case of a SHORT DUMP:
if the following perform statement should lead to a short dump, then
the report stated in the short dump is missing (RKEAK9Rsssmmmnnnn)
Check if table K9Rsssmmmnnn exists. If not it should be transported
from the original system.
Regenerate the missing reports by using transaction SE37, entering
function KEDR_REGENERATE_ALL_REPORTS and pressing button 'Test' and
'Execute'.
but I tried to run function KEDR_REGENERATE_ALL_REPORTS in SE37 and the problem persists.
Maybe I'm not running it correctly - there is no execute option when pressing "Test" so I enter the function and press F8, which takes me to a screen titled "Test function module" and then I execute.
My suspicion is that table "K9RECP3000001" cannot be created or generated since it it a system specific naming convention K9RSSSCCC0001 in which SSS is system ID (in our case ECP is production and ECQ is QA) ans CCC is client number (300 in prod, and should be 286 in ECQ).
Has anyone encountered this type of a problem and knows how to fix it?
Needless to say, I looked at OSS notes, but did not find the solution there.
Any thought will be appreciated,
Yoel.

Shalom Yoel,
This problem may be caused by the fact that some derivation rules
that were originally created once in a system have been transported
into target system without transporting the dependent objects
as well (the generated tables for the derivation rule entries).
You can see this by execution of program RKEDRCHECK with only
parameter 'Check in all clients' marked. You will then get
inconsistent derivation steps (which refer to a generated table
table for the rule entries that doesn't exist because it was
not transported).
There are two ways to solve the problem:
1.) If you don't need these steps any more in derivation you can get
    rid of them by executing program RKEDRCHECK with both parameters
    marked ('Check in all clients' and 'Delete inconsistent steps').
2.) If these steps should remain you have to retransport the missing
    tables from the source system in which these tables have to exist
    (creating transport requests for the customizing of derivation by
    pushing on the 'Transport' icon in the source system in transactions
    KEDR and KEPC).
For each derivation step,the system generates a program RKEAK9R *
and a table K9R+ System ID+ Mandant+ a number of five figures
from the object number in KEDR.
br, Guido

Short dump in report generation for bex query

Hi,
I have e newly installed SAP NetWeaver 7.3 and I'm not able to run BEx-Queries. When I start transaction RSRT and try to generate the report for the selected bex query, I get the following short dump:
Category               ABAP Programming Error
Runtime Errors         RAISE_EXCEPTION
ABAP Program           SAPLRRSI
Application Component BW-BEX-OT
If I start the test in RSRV for that query I get:
Generation limits for the generated report
Unable to load report GPEM3XZBL2Y9VX9H6SN
Am I missing a profile parameter for that generartion limits or something else?
Thanks in advance!

Hi,
Check whether your SAP GUI is activated and installed correctly.
check following threads
Runtime error RAISE_EXCEPTION has occurred
Dump when activating Business Content 7.35
Thanks and regards
Kiran

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 while executing job SM:EXEC SERVICES for EWA alert generation

Hello All,
I'm getting short dump error while executing job SM:EXEC SERVICES for EWA alert generation.I'm using EHP1@SP22 of Sol Man.
Please find the logs
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASCABAP_TRANS__________073
" in include "RDSVASIABAP_TRANS__________073 " in
line 1782:
"Field "STATEMENT_SUMMARY001019" is unknown. It is neither in one of th"
"e specified tables nor defined by a "DATA" statement. "DATA" statement"
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
If anyone came across such kind of dump, please reply asap, due to this, i could not generate EWA report for R/3 system 6.04.
Thanks,
Anand.

>
Anand Tigadikar wrote:
> Thx Paul, but i already did checked this note and its not solving my issue
Dear Anand,
Did you perform a complete service definition replacement for SDCC/SDCCN as described in the note?
These are manual steps you need to perform on the system and are not code corrections.
I would suggest you perform it, if you have not, and check the SDCCN logs to review the process ran cleanly.
Note: Please make sure SDCC_OSS is functioning and a connection to SAP can be made before
deleting the service definitions.
If you have already replaced the service defintions on the Solution Manager system, then no point doing it again. However checking a note and applying it are not the same thing. So I am uncertain if you replaced the service definitions or not. The dump you are getting in SM:EXEC SERVICES suggests its due to a problem with the service definitons. The recommendation is to replace them according to the process described in SAP Note 727998. If you have not done so please do so.
If you have successfully replaced the service definitions are you still getting the same dump, or has it possibly changed?
Regards,
Paul

LCA03 generates short dump: DBIF_DSQL2_SQL_ERROR

Similar Messages

Maybe you are looking for