Short Dump in CO02 Transaction

Hi ,
     I am getting short Dump in CO02 Transaction . Please see following detail .
     Runtime Errors         MESSAGE_TYPE_X
    Trigger Location of Runtime Error
    Program                                   SAPLCOKO1
    Include                                     LCOKO1F4H
    Row                                         614
    Module type                             (FORM)
    Module Name                           ORDER_CHANGE
>>>>>       MESSAGE x901.                                             "n779835
Please help me.
Thanks in Advance.
Sai

Hi Sai,
I get an similar Error after I have upgrade from 6.20 to ERP6 EHP4. Could you solve your problem?
Tanks
Bernd
Syntax error in program "SAPLCOKO1 ".
The current ABAP program "????????????????????????????????????????" had
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLCOKO1 " in include "LCOKO1FW2 " in line 27:
"The data object "LS_REF" down not have a component called "OBMAT"."

Similar Messages

Short dump in every transaction during support pack import - Solution Mgr

I am in the middle of applying support packs SP13 and SP14 for Solution Manager. In SPAM, during the import, I received short dumps. I get short dump for all transactions. The error message is 'Syntax error in program "SAPLWB_CUSTOMIZING", Field "G_DC_TABSTR" is unknown in INCLUDE LWB_CUSTOMIZINGDEV'.
Please help. Thanks !

Hi
My first question, would be, why are you performing other activities while importing patches?
This is not recommended.
Rahul

CONNE_IMPORT_WRONG_COMP_TYPE short dump in DB02OLD transaction

Hi,
We have recently upgraded to SAP ECC 6.0 and in solution manager system, I am getting CONNE_IMPORT_WRONG_COMP_TYPE short dump for DB02OLD transaction (Program RSORAT5M).
I searched few notes like 657981 and others but all are applicable for DB02 transaction. If anyone encountered same problem, please let me know how to resolve the issue.
Thanks in advance,
Ni3

Solved on my own

Short dumps in every transaction during the Support pack import

I am in the middle of applying support packs SP12 on NetWeaver 7.0. In SPAM, during the import, I received short dumps. I get short dump for all transactions i excute now. I am unable to go to SPAM to continue the SPAM, all I get short dumps. This is our new training system that we are building. I had same issues before, and I got help from SAP for this issue, where they suggested tp command wiht lots of options to run at the OS level. Since I moved company I am not able access the same ticket. Do anyone of you guys know the OS tp command to continue the SPAM import phase?
Please and thanks
Kumar

Hi,
SAP does not recommend to run SP's at OS level. Most of time when u r running SAP_BASIS , u will receive ABAP dumps. then option is to run SP at using tp command & you have to analyze many things before running this command.
<removed_by_moderator>
Please read the Rules of Engagement
Edited by: Juan Reyes on Jul 28, 2008 10:12 AM

Short Dump in MIGO transaction

When executing the transaction MIGO the transaction ends with the short dump as follows.
is it because of SAPNOTE 385830 ?
short text of error message : GET_SYTEM_BUSINESS_ERROR An error occurred while determining the business system ( No_business_system)
Technical information of error message
messgae class 00
number 001
variable 1 GET_SYTEM_BUSINESS_ERROR An error occurred while
variable 2 determining the business system ( No_business_system)
T CODE : migo
PROGRAM : SAPLMBWL
sceen no saplmigo 0001
screen line 18
the dump occurs at the line marked with -
>.
function mb_post_goods_movement.
""Local Interface:
*" IMPORTING
*"     VALUE(XBLNR_SD) OPTIONAL
*" EXPORTING
*"     VALUE(EMKPF) LIKE EMKPF STRUCTURE EMKPF
   data: l_mem_id(10) type c.                                   " 641365
Wurde zuvor eine Lieferung erzeugt, so ist kein MB_POST... nötig "HUM
   check not xdeliv = x.                                            "HUM
Control posting for external WM: Exit if BFWMS = 1 (Create delivery)
   check not mkpf-bfwms = 1.                                     "357661
   read table xmseg index 1.
   if not sy-subrc is initial.
     message a260.
   endif.
   if xmkpf-mblnr is initial.
     message a260.
   endif.
   xcommit = x.                                             "Performance
   if not xblnr_sd is initial.
     xmkpf-xblnr    = xblnr_sd.
     xmkpf-le_vbeln = xblnr_sd.                                 "XAN-SPM
     modify xmkpf index 1.
   when a goods movement for an inbound or outbound delivery is posted
   directly from VL31N/ VL01N, XBLNR is not yet known when we call
   CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
   BKPF as well. There is no other way to forward XBLNR to FI as not
   every document is posted by MB_CREATE -> a new function module in
   MBWL for transferring the information, called by FI, meant to load
   the complete function group for all MBxx postings when this isn't
   required (Performance). Would be the better way to transport the
   information after switching off MBxx in later release.
   corresponding IMPORT ... FROM MEMORY ... can be found in
   AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
     l_mem_id = 'MKPF-XBLNR'.                                   " 641365
     export xblnr = xblnr_sd to memory id l_mem_id.             " 641365
   endif.
   if xmkpf-xabln is initial.                               "note 434093
       call function 'MB_XAB_NUMBER_GET'.                   "note 434093
   endif.                                                   "note 434093
enhancement-point mb_post_goods_movements_01 spots es_saplmbwl static.
$$-Start: MB_POST_GOODS_MOVEMENTS_01----
$$
enhancement 26 dimp_general_saplmbwl.    "active version
data: l_statics_lock type c.
endenhancement.
$$-End:   MB_POST_GOODS_MOVEMENTS_01----
$$
enhancement-point mb_post_goods_movements_02 spots es_saplmbwl.
$$-Start: MB_POST_GOODS_MOVEMENTS_02----
$$
enhancement 25 dimp_general_saplmbwl.    "active version
read table xvbfa index 1.
if sy-subrc is initial and
   g_vbtyp_v = '7'.
   perform get_mdiff_kenz(sapmm07m) changing l_statics_lock.
endif.
endenhancement.
$$-End:   MB_POST_GOODS_MOVEMENTS_02----
$$
   call function 'MB_CREATE_MATERIAL_DOCUMENT_UT'
        exceptions
          error_message = 4.
As soon as we have started to put things into UPDATE TASK, we must
ensure that errors definitely terminate the transaction.
MESSAGE A is not sufficient because it can be catched from
external callers which COMMIT WORK afterwards, resulting in
incomplete updates. Read note 385830 for the full story.
   if not sy-subrc is initial.
message id sy-msgid type x number sy-msgno with            "385830
                 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    MESSAGE A263.
   endif.
Optische Archivierung
Spaete Erfassung mit Barcode
Redesign of barcode handling -> note 780365
perform barcode_update(sapmm07m) using xmkpf-mblnr
                                         xmkpf-mjahr
                                         barcode.
move-corresponding xmkpf to emkpf.
call function 'MB_MOVEMENTS_REFRESH'
    exceptions
      error_message = 4.
   move-corresponding xmkpf to emkpf.
   call function 'MB_MOVEMENTS_REFRESH'
        exceptions
          error_message = 4.
   if not sy-subrc is initial.
     message id sy-msgid type x number sy-msgno with             "385830
                sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
   MESSAGE A261.
   endif.
   perform buchen_initialisieren(sapmm07m).
   clear emkpf-subrc.
clear global fields when COMMIT WORK                     "Performance
   if not sy-oncom = p.
     perform clear_xcommit on commit.
   else.
     perform clear_xcommit.              "if this FB is called on commit
   endif.
   perform clear_xcommit on rollback.                       "note 303392
endfunction

hi
check SAP Note 556000 - Short dump due to note 385830
Summary
Symptom
   Consider the subsequent note 561872 !                             *
You want to post a goods receipt for a reference document (for example purchase order, delivery ...). The checks do not cause any error. Nevertheless, the system generates a short dump which is deliberately triggered by note 385830.
One known scenario is a stock transfer process via a delivery: You have entered a stock transport order assigned to a sales order and post a goods receipt for the delivery via transaction MIGO. The sales order must be in valuated. The material to which postings are to be made is valuated separately and to be handled in batches. And the batch, which was assigned via the delivery, already exists with a valuation type in the receiving plant which is different from the one specified in the purchase order.
Other terms
MB_CREATE_GOODS_MOVEMENT, MIGO, MCHA, BWTAR.
Reason and Prerequisites
Prerequisites: see above. This is a program error.
Solution
Implement the attached program corrections.
Then implement the subsequent note 561872.
After the implementation of the note, checks are carried out in the program flow - if a batch and a valuation type were entered for a goods movement (for instance with reference to the purchase order or delivery) - on whether the assignment of the batch and valuation type is correct.
regards
KI

Short dump in Z transaction code

Hi,
We have a Z transaction code 'ZPROFIT' for a report. After executing the report from output screen of report if i type 'se38' in command bar and if I press enter key it is going to short dump. But if I type '/nse38' it is working fine.The short dump description is as follows .
ShrtText
    An exception that could not be caught occurred.
What happened?
    The exception 'CX_SALV_OBJECT_NOT_FOUND' was raised but was not caught at any
     stage in the
    call hierarchy.
    Since exceptions represent error situations, and since the system could
    not react adequately to this error, the current program,
     'CL_SALV_FUNCTIONS=============CP', had to
    be terminated.
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assinged to the class 'CX_SALV_OBJECT_NOT_FOUND', was
     not caught,
    which led to a runtime error.
    The reason for this exception is:
    No text available for this exception
Trigger Location of Exception
    Program                                 CL_SALV_FUNCTIONS=============CP
    Include                                 CL_SALV_FUNCTIONS=============CM00J
    Row                                     28
    Module type                             (METHOD)
    Module Name                             IS_SALV_FUNCTION
Source Code Extract
Line SourceCde
    1 method is_salv_function.
    2   data: l_name      type string.
    3   data: l_msgtext   type string.
    4   data: ls_message type scx_t100key.
    5
    6 *get item
    7   try.
    8       call method get_item
    9         exporting
   10           function = name
   11         importing
   12           salv_function = value.
   13     catch cx_salv_object_not_found.
   14     try.
   15       call method get_group
   16         exporting
   17           group = name
   18         importing
   19           salv_function = value.
   20       catch cx_salv_object_not_found.
   21         l_name = name.
   22         message w026(salv_exception)
   23           with 'CL_SALV_FUNCTIONS' 'IS_SALV_FUNCTION' 'Function: ' l_name
   24           into l_msgtext.                                     "#EC NOTEXT
   25
   26         ls_message-msgid = sy-msgid.
   27         ls_message-msgno = sy-msgno.
>>>>>         raise exception type cx_salv_object_not_found
   29           exporting
   30             textid   = ls_message
   31             object   = 'Function'
   32             key      = l_name
   33             class    = 'CL_SALV_FUNCTIONS'                    "#EC NOTEXT
   34             method   = 'IS_SALV_FUNCTION'.                    "#EC NOTEXT
   35     endtry.
   36   endtry.
   37
Please let me know how we can solve this?
Is there anything wrong in report source code?
Thanks in advance.
Regards,
Brahma Reddy

hi brahma,
try to reinstall ur Front End...
it's not a error from ur Program, I think it's dumb because SAP GUI it's not all right working,
try to remove and install SAP GUI, maybe it's can solve ur problem...
Regards
Allan Cristian

Short Dump with VA22 transaction in ECC 6

Hi All,
We are on ECC 6 and facing a short dump whenever we are trying to save some quotation. We are getting the following error.
There is probably an error in the program "SAPLSYDB". The program is triggered in the update task. There, the following ABAP/4 statements are not allowed:
CALL SCREEN
CALL DIALOG
CALL TRANSACTION
SUBMIT
"POSTING_ILLEGAL_STATEMENT" " "
"SAPLSYDB" or "LSYDBU27"
"DB_COMMIT".
Is there a sap note for this. Any link or pointer to this will be highly appreciated.
Regards,
Jayant

Hello,
This looks like a problem for SAP. I assume that you have not modified the
program SAPLSYDB. I also assume that you have searched the Service Marketplasce
for any OSS notes. My next step would be to create a message to SAP to get them to
have a look.
Regards
Greg Kern

Short dump with the transaction CJ02

Hello, this is my first thread in the forum. I hope to solve my problem.
It is necesary to say you that my english is very poor, is not so good. Sorry for that.
When i use the transaction CJ02 to finish or close a project, appears an error when i save it. The steps are the followings:
1- Run the transaction CJ02 with a WBS element
2- Mark the line of the WBS element
3- Select then button Settlement rule
4- Fill 4 items in the next screen to distribution rules (the % is 100)
5- Back with green arrow
6- Fill the field Cost Center Req
7- Save
After a few seconds appears the dump:
<b>ABAP runtime errors    MESSAGE_TYPE_X
       Occurred on     20.11.2006 at 11:07:09
>> Short dump has not been completely stored. It is too big.
The current application triggered a termination with a short dump.
Error analysis
Short text of error message:
Nested call of PERFORM ON COMMIT:
Long text of error message:
Diagnosis
     During processing of a routine called using PERFORM ... ON COMMIT,
     the system attempted to call PERFORM ... ON COMMIT again. Nesting
     of this is not allowed.
System Response
Procedure
     The program indicated after "Caller:" must be changed. This is the
     program that calls the routine indicated after "Form:" during
     COMMIT processing. This routine is part of the program indicated
     after
     "Program:".
Procedure for System Administration
Technical information about the message:
Message classe...... 00
Number.............. 081
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
If the error is in one of your own ABAP programs or an SAP program that
you have modified, try to correct it.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"MESSAGE_TYPE_X"
"SAPMSSY0 " or "SAPMSSY0 "
"%_ORDER_FORM_FOR_ROLLBACK"</b>
There are several notes that apparently solve the problem with support packages that are applied in our system (for example 397011 or 614553). Inthis case our system is updated.
Can you help me please.
Thanks
Gabriel.-

Hi
Are you really sure https://websmp101.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=397011&_NLANG=E
is applied correctly ?
Try downloading with snote and see if it gets marked 'not relevant',
( are you on release 4.6 ? )
Given the nature of the problem ( and the fact that this issue is known ) , the best seems log an OSS support request
rgds
Dirk

Short dump during ME23N transaction due to missing field in KOMP table

Hi All,
We have just upgraded to Business Suite 7.0 and are experiencing the following error:
Short dump during processing of transaction ME23N - error is in program SAPLV61A when the system calls the following field: KOMP_SERVICE_PARAM2 (this does not exist in KOMP). We need to get this resolved as soon as possible, It appears that SAP have removed this field from the table KOMP but the standard programme is still looking for this field. Can anyone provide an oss note number or insight into how to resolve this issue please.
Many Thanks
Amanda

Dear,
This problem is caused by a missing initialization of the structure KOMP in the program SAPLV61A.
The problem may also occur during , when the "Create PO automatically" indicator (TVAP-ALEKZ) is set for the relevant item category in the item category Customizing (transaction VOV7). In this case, the data of the purchase order item that was previously processed is used for the back update of the sales order from the purchase order in KOMP.
Add the following import parameter to the function module RV_KONV_SELECT:
    Parameter name        COMM_ITEM_I
    Typing          LIKE
    Associated type            KOMP
    Optional        X
    Pass Value       X
Please refer the OSS note 1261566.
Regards,
R.Brahmankar

Short dump in every transaction during support pack import In PRD server

HI
While trying to applying support pack stack, get short abap dump, but after this in every tx same dump is there.
Following is the Support stack that we are applying
SAPKA70020
SAPKB70020
SAPKIPYM10
SAPKW70022
SAPKNA7017
SAPKH60012
SAPK-60008INFINBASIS
SAPKGS6008
following is dump
Syntax error in program "SAPLPA_PACKAGE_SERVICES
Error in the ABAP Application Program
The current ABAP program "SAPLSFW_COMMON" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLPA_PACKAGE_SERVICES " in
include "CL_PACKAGE_HELPER=============CU " in
line 179:
"Type "SLS_PACKAGE_INFO" is unknown"
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 "SAPLSFW_COMMON" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Thanks
YogRaj

Hi
I have applied support Pack successfully. But after this my one of SD user getting short dump in Tx VL01N, VA01.
Syntax error in program "SAPLDG95 "
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_IM_EHS_DG_002_IMPL=========CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPLDG95 " in include "LDG95U01
     " in
    line 29:
    ""X_DGMSD_TAB" and "E_DGMSD_TAB" are not mutually convertible. In Unico"
    "de programs, "X_DGMSD_TAB" must have the same structure layout as "E_D"
    "GMSD_TAB", independent of the length of a Unicode character."
    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 "CL_IM_EHS_DG_002_IMPL=========CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    The following syntax error was found in the program SAPLDG95 :
    ""X_DGMSD_TAB" and "E_DGMSD_TAB" are not mutually convertible. In Unico"
    "de programs, "X_DGMSD_TAB" must have the same structure layout as "E_D"
    "GMSD_TAB", independent of the length of a Unicode character."
Thanks
YogRaj

Short dump CONVT_CODEPAGE in transaction I18N

Hi,
I'm trying to install the french language into a Solution Manage 4.0 system.
SQL Server 2005 database + Windows 2003 X64
When I run I18N > I18N Menu > I18N Customizing > I18N System Configuration in order to activate french I have a dump (more details bellow).
Same error when I try to run report RSCPINST.
I'm running out of idea, I'm unable to find a way to solve this issue, anybody can help me ?
Thanks in advance,
V.Ch.
Short dump long text :
Runtime Errors         CONVT_CODEPAGE
Except.                CX_SY_CONVERSION_CODEPAGE
Date and Time          21.01.2008 22:02:16
Short text
A character set conversion is not possible.
What happened?
At the conversion of a text from codepage '4110' to codepage '4103':
- a character was found that cannot be displayed in one of the two
codepages;
- or it was detected that this conversion is not supported
The running ABAP program 'SAPLSCP2' had to be terminated as the conversion
would have produced incorrect data.
The number of characters that could not be displayed (and therefore not
be converted), is 1. If this number is 0, the second error case, as
mentioned above, has occurred.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_CODEPAGE', was not
caught in
procedure "CHECK_PROFILE" "(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:
Characters are always displayed in only a certain codepage. Many
codepages only define a limited set of characters. If a text from a
codepage should be converted into another codepage, and if this text
contains characters that are not defined in one of the two codepages, a
conversion error occurs.
Moreover, a conversion error can occur if one of the needed codepages
'4110' or '4103' is not known to the system.
If the conversion error occurred at read or write of screen, the file
name was 'G:\usr\sap\L1D\SYS\profile\DEFAULT.PFL'. (further information about
the file: "X 2673")
Missing RAISING Clause in Interface
Program                                 SAPLSCP2
Include                                 LSCP2U23
Row                                     103
Module type                             (FORM)
Module Name                             CHECK_PROFILE
Trigger Location of Exception
Program                                 SAPLSCP2
Include                                 LSCP2U23
Row                                     142
Module type                             (FORM)
Module Name                             CHECK_PROFILE
Source Code Extract
Line
SourceCde
112
fname = a_profilefilename.
113
parname = a_parname.
114
115
open dataset fname for input in text mode encoding default.
116
do.
117
read dataset fname into rec1.
118
if sy-subrc <> 0.
119
if sy-subrc = 8.
120
rec3 = 'OpenErr'.
121
exit.
122
elseif sy-subrc = 4.
123
rec3 = 'NotIn'.
124
exit.
125
else.
126
rec3 = 'rcNot0.'.
127
exit.
128
endif.
129
else.
130
if rec1 np '##*' and
131
rec1 cs parname.
132
rec3 = rec1.
133
exit.
134
endif.
135
endif.
136
enddo.
137
close dataset fname.
138
139
fname = a_defaultfilename.
140
open dataset fname for input in text mode encoding default.
141
do.
>>>>>
read dataset fname into rec1.
143
if sy-subrc <> 0.
144
if sy-subrc = 8.
145
rec2 = 'OpenErr'.
146
exit.
147
elseif sy-subrc = 4.
148
rec2 = 'NotIn'.
149
exit.
150
else.
151
rec2 = 'rcNot0.'.
152
exit.
153
endif.
154
else.
155
if rec1 np '##*' and
156
rec1 cs parname.
157
rec2 = rec1.
158
exit.
159
endif.
160
endif.
161
enddo.

Hi,
Check [this note.|Note 990971 - Error in character conversion:CX_SY_CONVERSION_CODEPAGE dump] This will solve your problem.
Feel free to revert back.
--Ragu

Short dump in VF01 transaction with error id SAPSQL_ARRAY_INSERT_DUPREC

Hi,
We are getting shortdump SAPSQL_ARRAY_INSERT_DUPREC when running VF01 transaction.
The ABAP/4 Open SQL array insert results in duplicate database records.
The termination occurred in the ABAP/4 program "SAPLV60U " in
"VBUK_BEARBEITEN".
Line Number 536
>>>>> INSERT vbuk FROM TABLE da_xvbuki.
Could some one please reply me when you have the time.
Regards,
Vishal
Moderator Message: De-prioritized.
Edited by: kishan P on Aug 29, 2011 2:05 PM

Duplicate records is being tried to enter in table VBUK, which is not allowed due to primary key concept. Hence the error.
For details, you can get help of the technical person in your team

Short dump in LB10 transaction

Hi all,
In ECC 6 by LB10 Create Transfer Order from Transfer Requirement, When click Save to create a transfer order for putaway get error, and it showing Runtime Error GETWA_NOT_ASSIGNED and Short text Field symbol has not yet been assigned. any one can suggest me, what can be done to rectify this error.
Thanks in Advance
Srikanth

Hi Sudheer,
Thanx for your replay, but iam getting error
while edit parameters of table used for ALV output in report RLVSDR20.
code is If i_create_itab = con_x.
here i_create_itab is not a field symbol it's an importing parameter of a Function module (L_PRINT_PARAM_FIND_40) , which used in above ALV progarm.
Thanx in Advance

In SMARTFORMS when openee a Text Node,   Giving a Short Dump

Hi
I am getting Short Dump in SMARTFORMS Transaction, when ever I opened a Text Node and made some changes in it.
With out opening a Text Node I can able to change and activate the SmartForm.
But if I open a Text Node I can able to make changes in the Text Node but later if i click on any other Node, it is giving a Short Dump.
But all other systems in my office are working fine.
I have tried the Utilities->Settings-> and changed the editor also.
I have also Installed the SAPGUI once again for this Issue. But still I am getting the same problem.
Can anyone Please help me on this Issue.
I am sending the error enalysis of the Short Dump.
Error analysis
    Short text of error message:
    Control Framework : Error processing control
    Long text of error message:
     Diagnosis
         An error occurred when the system tried to process the commands
         from the Automation Queue on the presentation server.
         There are several possible reasons for this:
         - The installation of the SAP GUI on the presentation server is
         faulty or obsolete.
         - There is an error in the application program
         - There is an error in the SAPGUI or an integrated control
     Procedure
         1. Make sure that you have imported the appropriate Support
         Package, the current kernel, and GUI patch for the release of your
         system
         2. Check whether the error occurs locally on one or a few PCs, or
         generally on all PCs. Note whether the error only occurs for some
         users, for example because of a specific Customizing setting.
         If it only occurs locally, this suggests an installation problem
         with the PC. Check the installation; if necessary, reinstall the
         software. In the dump, search for the SY-MSGLI field, since it may
         point to the cause of the error.
         3. Activate the Automation Trace (in accordance with SAP Note
         158985).
         4.Start the transaction and continue until the screen immediately
         before the dump.
         5. From the System -> Utilities menu, choose Autom. Queue,
         Synchronous Processing.
         The status bar of the GUI displays the text:
            "Automation synchron flush mode on"
         6. If you now proceed with the application, the short dump will
         display the ABAP call that caused the error; the Automation Trace
         will contain the error on the presentation server.
         7. If necessary, load the short dump and trace files on to
         sapservX, so that SAP can analyze them.
    Technical information about the message:
    Message class....... "CNDP"
    Number.............. 006
Thanks in Advance.

Hi
I think dump is because of SAP GUI. If you are ECC 6.0 then install SAP GUI 710 with patch level 2 or more and check
Regards
Shiva

Short dumps while using J3A9 & VK12

We are implementing SAP ECC 6.0 and are experiencing short dumps while using transactions J3A9 and VK12. They all point to program /AFS/SD_DISP_CONDITION_TABLE and related Includes. I haven't found any information regarding this program on this site or in OSS, mostly due to the fact that the program is only 2 months old, which is troubling enough...
If anyone is experiencing similar issues, please feel free to respond. I have opened an OSS note with SAP and they are having trouble recreating the issue as it doesn't happen consistently.
Thanks and best regards,
Chris Mowl

We are implementing SAP ECC 6.0 and are experiencing short dumps while using transactions J3A9 and VK12. They all point to program /AFS/SD_DISP_CONDITION_TABLE and related Includes. I haven't found any information regarding this program on this site or in OSS, mostly due to the fact that the program is only 2 months old, which is troubling enough...
If anyone is experiencing similar issues, please feel free to respond. I have opened an OSS note with SAP and they are having trouble recreating the issue as it doesn't happen consistently.
Thanks and best regards,
Chris Mowl
10/22/08: Several OSS notes have been created regarding this issue but none of them have solved it. The two most recent notes are 1262962 & 1225190. If you are having this problem. start with these notes.

Short Dump in CO02 Transaction

Similar Messages

Maybe you are looking for