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

Similar Messages

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 ALV Report

Hi
I have one Zreport which gives the result in ALV form.
After getting the result(1 row with 33 columns) when I tried to export the ALV results to spread sheet using the option : List-> Export-> Spread Sheet OR by click on Excel icon in the display screen,I'm getting the short dump with the description "No more storage space available for extending an internal table" .
After analysis ,find that dump is raising in the FM : F4_GET_RESULT of Include Program : LSDH3U03.
Can anyone provide us some clue .
Thanks & Regards,
Sreeram

Hi,
If the display is in ALV grid format, then you can try another approach to save the data in a spreadsheet.
- Right-click on any output cell.
- Select 'Spreadsheet' from the drop down list
- radio-button 'All available formats'
- Excel (In existing XXL format)
Thanks!
VS.

CSAP_MAT_BOM_OPEN Short Dump with CONVERT_MATNR_TO_INTERN_FORMAT

Has anyone else had this issue? All help appreciated.
I am using the function CSAP_MAT_BOM_OPEN to update a BOM. Running it generates a short dump with the following information:
In PERFORM or CALL FUNCTION "CONVERT_MATNR_TO_INTERN_FORMAT", the actu
al parameter "MATERIAL" is incompatible with the formal parameter "I_M
ATNR".
At first I thought my variable for the material number was bad so instead I gave it a literal value just to see if it gave me a problem and it did.
Here is the snippit of code from my program where I give it an actual value:
   call function 'CSAP_MAT_BOM_OPEN'
        exporting
             material = '000000000000123456'
             plant = '1000'
             bom_usage = '3'
             valid_from = '20140703'
        importing
             o_stko     = tstk2
             fl_warning = flg_warning
        tables
             t_stpo     = tstp2
        exceptions
             error      = 1.
Inside this SAP owned FM is the following:
   perform convert_matnr_to_intern_format using material
                                          changing csin-matnr
                                           hlp_subrc.
convert_matnr_to_intern_format says this:
form convert_matnr_to_intern_format
                             using value(i_matnr) like csap_mbom-matnr
                             changing o_matnr like csin-matnr
                                      value(subrc) like sy-subrc.
   data: conversion_call(30) type c value 'CONVERSION_EXIT_?_INPUT',
         conve(5)            type c,
         conv_exit(10)       type c.
   clear subrc.
   check not i_matnr is initial.
   describe field csin-matnr edit mask conv_exit.
   move conv_exit+2(5) to conve.
   replace '?' with conve into conversion_call.
   call function conversion_call
        exporting
             input        = i_matnr
        importing
             output       = o_matnr
        exceptions
             not_found    = 04
             length_error = 08
             too_long     = 12
             wrong_mask   = 16.
   subrc = sy-subrc.
endform.

Hi Richard,
in fm CSAP_MAT_BOM_OPEN there is a single call of form convert_matnr_to_intern_format:
   perform convert_matnr_to_intern_format using material
                                          changing csin-matnr
                                                   hlp_subrc.
where material is defined in the fm interface:
function csap_mat_bom_open.
*"*"Lokale Schnittstelle:
*" IMPORTING
*"     VALUE(MATERIAL) LIKE CSAP_MBOM-MATNR
In the form interface I_MATNR in include LCSAPFC1 is defined identically:
form convert_matnr_to_intern_format
                             using value(i_matnr) like csap_mbom-matnr
                             changing o_matnr like csin-matnr
                                      value(subrc) like sy-subrc.
So importing parameter of type CSAP_MBOM-MATNR is passed to field I_MATNR of type CSAP_MBOM-MATNR and there can't be any type conflict, if
there is no modiffication in your system
fm CSAP_MAT_BOM_OPEN and include LCSAPFC1 are active
no parts of function group CSAP have been overwitten by importing a transport request into your system
Please check this code snippets against those in your system.
What can you do, if all is looking okay:
Check the version history (fm and include) for suspicious transport requests.
If no transport requests found, try to regenerate the fm, th include and the whole function group.
Regards,
Klaus

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 with TPM_TRD1 000

hi everyone,
when I run the Tcode:TBB1，i come across a ABAP short dump error.
my system environment is:
PC
windows2003NT
oracle10.2
independant system without SLD control
The error info as follow:
Note 837202 - TPM_MIGRATION:tpm18: Short dump with TPM_TRD1 000
Summary
Symptom
You migrate from Release CFM or Enterprise 1.10 to ERP 2.0 or higher. There are already parallel valuation areas in use. In tpm_migration_cat, you specify a key date. In the test system, the following short dump occurs for the parallel valuation areas:
Error message short text:
Internal error: SLD
Message class: "TPM_TRD1"
Number: 000
Variable 1: "SLD"
Other terms
CL_DISTRIBUTOR_SLD, TPM_TRD1000
Solution
In the production system, you have to carry out tpm18 before the technical upgrade for all business transactions that are before the key date from tpm_migration_cat.
I do not understand how to do with the soluton
eg.what is "tpm18"?
Do need your helps,
Thank you very much
Peter

Hi Peter,
I guess you found note 837202 when you were looking for a solution for the TBB1 dump you encountered.
This note deals with a special situation when executing tpm18 (which is the transaction for fixing and posting derived flows) in a test system after migration and it tells you you should run tpm18 in production before the technical upgrade.
I am not sure if this really applies to your situation, maybe you should rather check if note 821854 and the solution therein can be helpful.
But without more information (e.g. knowing more about your release, your 'migration history' and the part of the coding where the dump is raised), it is quite difficult to give a diagnosis.
Maybe you should think of sending a customer message to SAP support via the SAP marketplace if you cannot get rid of this problem on your own.

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 with an error SAPSQL_LIKE_QUOTES

Hi,
today we have more short dumps with an error SAPSQL_LIKE_QUOTES. this means The logical condition contains a text field literal, for which there is no closing quotation mark.
as per my analysis i found the below code from the std. sap program SAPLBTCH in that include LBTCHF19.
TRANSLATE p_buffer1 USING '*%'.
IF p_buffer1 CO '% '.
    IF NOT i_mandatory IS INITIAL.
      CONCATENATE i_name '<> ''''' INTO o_where
        SEPARATED BY space.
    ENDIF.
    EXIT.
ENDIF.
can you please tell me that there is a sapce in the line IF p_buffer1 CO '% '.
please advice me if this statement is true or should not contain any spaces between the quotations.
Thanks,
Kasi

Hi Kasi,
please check this link
[SAPSQL_LIKE_QUOTES|http://www.google.com/#hl=en&num=100&q=SAPSQL_LIKE_QUOTES&fp=1&cad=b]
Kind regards,
Clemens

Transport with return code 12 ,short dump with 'DBIF_RSQL_SQL_ERROR'

Dear All,
My trasnport contains infoprovider. DTP,transpformations, character realtionships , aggregation levels ,web templates, programs.
I got a transport failed with Return code 12, and it is showing message :
Program terminated (job: RDDEXECL, no.: 06031600)
See job log
Execution of programs after import (XPRA)
End date and time : 20101026060421
Ended with return code: ===> 12 <===
I have short dump with 'DBIF_RSQL_SQL_ERROR' exception 'CX_SY_OPEN_SQL_DB'.
in how to correct the error :
below is the detials.
Database error text........: "ORA-01578: ORACLE data block corrupted (file #
211, block # 79950)#ORA-01110: data file 211:
'/oracle/RBW/sapdata15/xbw_188/xbw.data188'#ORA-26040: Data block was loaded
using the NOLOGGING option"
did someone has the same problem .
Help is really appreciated.
Regards
Veera

I am afraid you will need to esclate this to BASIS team.. seems some issue with database

Short dump with a select statement

I have the following select statement (I have also inluded my data statement(s)) and I get a short dump. The error is as follows:
<b>What happened?
    Error in ABAP application program.
The current ABAP program "ZPARTNER" had to be terminated because one of the
    statements could not be executed.
This is probably due to an error in the ABAP program.
Following a SELECT statement, the data read could not be placed in AN
    the output area.
    A conversion may have been intended that is not supported by the
    system, or the output area may be too small.
Error analysis
    An exception occurred. This exception will be dealt with in more detail
    below. The exception, assigned to the class 'CX_SY_OPEN_SQL_DB', was not
     caught, which
     led to a runtime error. The reason for this exception is:
    The data read during a SELECT access could not be inserted into the
    target field.
    Either conversion is not supported for the target field's type or the
    target field is too short to accept the value or the data are not in a
    form that the target field can accept          </b>
it_adrc TYPE TABLE OF adrc,
      wa_adrc LIKE LINE OF it_adrc,
SELECT addrnumber name1 street city1 region post_code1 tel_number
FROM adrc INTO TABLE it_adrc
FOR ALL ENTRIES IN it_detail
WHERE addrnumber = it_detail-adrnr.
Regards,
Davis

If you only need the fields mentioned in the select query, then follow this:
TYPES: BEGIN OF ADRC_TYPE,
     ADDRNUMBER LIKE ADRC-ADDRNUMBER,
     NAME1        LIKE ADRC-NAME1,
     STREET        LIKE ADRC-STREET,
     CITY        LIKE ADRC-CITY,
     REGION        LIKE ADRC-REGION,
     POST_CODE1 LIKE ADRC-POST_CODE1,
     TEL_NUMBER LIKE ADRC-TEL_NUMBER,
       END OF ADRC_TYPE,
       ADRC_T_TYPE TYPE TABLE OF ADRC_TYPE.
DATA: IT_ADRC TYPE ADRC_T_TYPE WITH HEADER LINE.
IF NOT IT_DETAIL[] IS INITIAL.
SELECT addrnumber name1 street city1 region post_code1 tel_number
FROM adrc INTO TABLE it_adrc
FOR ALL ENTRIES IN it_detail
WHERE addrnumber = it_detail-adrnr.
ENDIF.
Thanks,
SKJ

Short dump with error RSW_CURRENCY_TRANSLATION while loading SRM data

Hi All,
I am loading data from SRM to BW. From data source 0BBP_TD_CONTR_2 to DSO 0SRCT_DS1. Data is loaded from source to PSA. When loading from PSA to DSO using DTP, I am getting a short dump with below error. Can one please let me know solution if you have faced the same problem previously?
Termination occurred in the ABAP program "SAPLRSW0" - in
"RSW_CURRENCY_TRANSLATION".
The main program was "RSBATCH_EXECUTE_PROZESS ".
In the source code you have the termination point in line 86
of the (Include) program "LRSW0U09".
The program "SAPLRSW0" was started as a background job.
I have checked the DSO routines and objects, everything is ok. Replicated all currency conversion tables from source.
0PSTNG_DAT infoobject is also active. There is no errors in Development while loading, when moved to quality, the error is throwing.
Regards,
Don

Hi All,
We need to activate 0SR_DEFCUR currency object. I have activated the object and transported. Issue is resolved.
Thanks to all for your kind replied.
Regards,
Don

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 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"."

Infospoke short dumps with MESSAGE_TYPE_X

Whenever one of our many infospokes are invoked and there is no data to pull from BW, the process short dumps with MESSAGE_TYPE_X in module RSB_API_OHS_DEST_READ_DATA.
Is anyone else experiencing this problem?

Hi,
Please take a look in note 1370227.
I hope this note help you.
Thanks,
Rafael

Short dump with the transaction CJ02

Similar Messages

Maybe you are looking for