Short Dump issue

Dear all,
hi,
i am working on upgrade from 4.6 to ECC6.
during unicode this statement is not working in ZReports.
IMPORT: it_vbrp FROM DATABASE indx(st) ID '1' ,
It is giving short dump. with message When importing object "IT_VBRP", the structure did not match the
structure of the target object. The error occurred in component
no. 3.
what should i do.
any help would be fine for me.
Thanks
Jairaj kumar

Similar Messages

ALV GRID short dump issue

could anybody advice, ALV GRID FM(field catalog issue)is getting short dump, but workig fine for ALV LIST.
PERFORM create_field_catalog USING:
    'TRAFFIC_LIGHT' ' ' 15 'Status'   'Status' ' ',
    'VKORG'     ' ' 15 'Sales Org'    'Sales Org' ' ',
    'VTWEG'     ' ' 15 'Dist Channel' 'Dist Channel' ' ',
    'KUNRG'     ' ' 15 'Payer'        'Payer' ' ',
    'PAYER'     ' ' 15 'Payer Name'   'Payer Name' ' ',
    'KUNAG'     ' ' 15 'Ship-To'      'Ship-To' ' ',
    'SHIPTO'    ' ' 15 'Ship-To Name' 'Ship-To Name' ' ',
    'SHIPTOPAR' ' ' 15 'Bill to Party' 'Bill To Party' ' ',
    'KDGRP'     ' ' 15 'Customer Grp' 'Customer Grp' ' ',
    'ZCUSTPO'   ' ' 15 'Customer PO' 'Customer PO' ' ',
    'VBELN'     ' ' 15 'Billing Doc' 'Billing Doc' ' ',
    'FKDAT'     ' ' 15 'Billing Date' 'Billing Date' ' ',
    'FKART'     ' ' 15 'Billing Type' 'Billing Type' ' ',
    'ZOUTPUT'   ' ' 15 'Output Type' 'Output Type' ' ',
    'NETWR'     ' ' 15 'Net Value'    'Net Value' 'X',
    'KWERT'     ' ' 15 'Total VAT'    'Total VAT' 'X',
    'WAERK'     ' ' 15 'Currency'     'Currency' ' ',
    'XBLNR'     ' ' 15 'Reference'    'Reference' ' ',
    'DELNO'     ' ' 15 'Delivery #'   'Delivery #' ' ',
    'TLINE'     ' ' 15 'Manifest #'   'Manifest #' ' ',
    'ZBOL'      ' ' 15 'Bill Of Ldng' 'Bill of Ldng' ' ',
    'LIFEX'     ' ' 15 'Ext Del #'    'Ext Del #' ' ',
    'POSNR'     ' ' 15 'Item'         'Item' ' ',
    'MATNR'     ' ' 18 'Material'     'Material' ' ',
    'KDMAT'     ' ' 15 'Cust Matl'    'Cust Matl' ' ',
    'WERKS'     ' ' 15 'Plant'        'Plant' ' ',
    'ZZPLAT'    ' ' 10 'Platform'     'Platform' ' ',
    'ZZPRONUM' ' ' 10 'Program'      'Program' ' ',
    'ZZPROCODE' ' ' 10 'Prod Code'    'Prod Code' ' ',
    'FKIMG'     ' ' 15 'Qty'          'Qty' ' ',
    'VRKME'     ' ' 15 'UoM'          'UoM' ' ',
    'ARKTX'     ' ' 15 'Description' 'Description' ' ',
    'KBETR'     ' ' 15 'Price'        'Price' ' ',
    'VATRT'     ' ' 15 'VAT Rate'     'VAT Rate' ' ',
    'KWERT_D'   ' ' 15 'Item VAT'     'Item VAT' 'X',
    'NETWR_D'   ' ' 15 'Item Net Value' 'Item Net Value' 'X',
    'VGBEL'     ' ' 15 'Ref Document' 'Ref Document' ' ',
    'VGPOS'     ' ' 13 'Ref Doc Line' 'Ref Doc Line' ' ' .
FORM create_field_catalog USING fieldname TYPE c
                                inttype   TYPE c
                                outputlen TYPE i
                                coltext   TYPE c
                                seltext   TYPE c
                                do_sum    TYPE c.
DATA: l_f_fieldcat TYPE slis_fieldcat_alv.
l_f_fieldcat-fieldname    = fieldname.
l_f_fieldcat-inttype      = inttype.
l_f_fieldcat-outputlen    = outputlen.
l_f_fieldcat-seltext_m    = coltext.
l_f_fieldcat-seltext_l    = seltext.
l_f_fieldcat-reptext_ddic = coltext.
l_f_fieldcat-do_sum     = do_sum.
APPEND l_f_fieldcat TO t_field_catalog.
CLEAR l_f_fieldcat.
ENDFORM.   "CREATE_FIELD_CATALOG
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          i_callback_program      = v_repid
          i_callback_user_command = 'F_USER_COMMAND'
          i_grid_settings         = f_grid_settings
          is_layout               = f_grid_layout
          is_print                = f_print_settings
          i_background_id         = 'BACK'
          it_events               = t_events[]
          it_fieldcat             = t_field_catalog
          it_sort                 = t_sortcat[]
          i_default               = 'X'
          i_save                  = 'A'
          is_variant              = f_variant
        TABLES
          t_outtab                = t_output4
        EXCEPTIONS
          program_error           = 1
          OTHERS                  = 2.

BEGIN OF t_output4 OCCURS 0,
        traffic_light TYPE c,
        vkorg LIKE vbrk-vkorg,
        vtweg LIKE vbrk-vtweg,
        kunrg LIKE vbrk-kunrg,
        payer LIKE adrc-name1,
        kunag LIKE vbrk-kunag,
        shipto LIKE adrc-name1,
        shiptopar LIKE likp-kunnr,
        kdgrp LIKE vbrk-kdgrp,
        zcustpo LIKE vbkd-bstkd,
        vbeln LIKE vbrk-vbeln,
        fkdat LIKE vbrk-fkdat,
        fkart LIKE vbrk-fkart,
        zoutput LIKE dnast-kschl,
        netwr LIKE vbrk-netwr,
        kwert LIKE konv-kwert,
        waerk LIKE vbrk-waerk,
        xblnr LIKE vbrk-xblnr,
        delno LIKE likp-vbeln,
        t_line LIKE tline-tdline,
        zbol LIKE likp-bolnr,
        lifex LIKE likp-lifex,
        posnr LIKE vbrp-posnr,
        matnr LIKE vbrp-matnr,
        kdmat LIKE lips-kdmat,
        werks LIKE vbrp-werks,
        zzplat LIKE vbrp-zzplat,
        zzpronum LIKE vbrp-zzpronum,
        zzprocode LIKE a802-zzprocode,
        fkimg LIKE vbrp-fkimg,
        vrkme LIKE vbrp-vrkme,
        arktx LIKE vbrp-arktx,
        kbetr LIKE konv-kbetr,
        vatrt TYPE p DECIMALS 1,
        kwert_d LIKE konv-kwert,
        netwr_d LIKE vbrp-netwr,
        vgbel LIKE vbrp-vgbel,
        vgpos LIKE vbrp-vgpos,
      END OF t_output4,

DTP Short dump issue

Hi Expert,
I face a DTP shortdump issue on loading data from PSA to DSO
The DSO is write optimize.
DTP is using symantic loading and support 3 processor, pack size is default
Situation is as below:
1. This issue occurs every two days. In some situation, it will occur everday
2. The DTP will face short dump. Then when we rerun the DTP, everything goes will
3. Not all the system face this issue (for example, we have dev/qas/prd, this issue cannot be reproduced in qas)
Below is the shortdump point in ST22
   when '3'.
      select single * from rsmonicdp into l_s_monicdp where
             rnr   = l_rnr and
             icube = p_ods and
             dp_nr = i_datapakid.
      if sy-subrc <> 0.
        data: l_s_iccont type rsiccont.
        data: l_s_reqdone    type rsreqdone.
        select single * from rsreqdone into l_s_reqdone where
               rnr = l_rnr.
        if sy-subrc <> 0.
          message x000.
        endif.
        l_s_reqdone-datum = l_s_reqdone-datum + 3.
        if l_s_reqdone-datum < sy-datum.
          select single * from rsiccont into l_s_iccont where
                 rnr   = l_rnr and
                 icube = p_ods.
          if sy-subrc <> 0.
            exit.
          else.
            message x000.
          endif.
        else.
           message x000. (Shortdump here)
        endif.
      endif.
      l_s_monicdp-status     = icon_red_light.
Could you kindly let me know you face simulation issue before and possible solution?
Thanks and best regards
Alex yang

Hi KP,
Thanks for your information.
Please check below information in ST22 side
Error analysis
    Short text of error message:
Status Manager *****
    Long text of error message:
    Technical information about the message:
    Message class....... "RSSTATMAN"
    Number.............. 000
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
    "MESSAGE_TYPE_X" " "
    "CL_RSSM_STATMAN_TARGET_ODSO===CP" or "CL_RSSM_STATMAN_TARGET_ODSO===CM007"
    "IF_RSBK_DATAPACKAGE_OBSERVER~UPDATE_STATUS_TABLES"
BTW, do you think this issue will be related to larger data volum in DSO side?
Thanks and best regards
Alex yang

Short dump issue while loading data

Hello All,
We are trying to load the data to the cube , but every time it is throwing us a short dump with the below error.
We have found a SAP Note as well for the below error , Please suggest, how to implement the same.
Error:
Runtime Errors         CONVT_NO_NUMBER
METHOD end_routine.
=== Segments ===
   FIELD-SYMBOLS:
     <RESULT_FIELDS>    TYPE _ty_s_TG_1.
   DATA:
     MONITOR_REC     TYPE rstmonitor.
   ... "insert your code here
-- fill table "MONITOR" with values of structure "MONITOR_REC"
-   to make monitor entries
   ... "to cancel the update process
    raise exception type CX_RSROUT_ABORT.
*Fiscal year quarter addition
   loop at RESULT_PACKAGE assigning <RESULT_FIELDS>.
     if <RESULT_FIELDS>-/bic/zsp_Mon BETWEEN 1 and 3.
       CONCATENATE 'FY' <RESULT_FIELDS>-fiscper+2(2) 'Q3' INTO
       <RESULT_FIELDS>-/bic/zsp_FYQA.
     elseif <RESULT_FIELDS>-/bic/zsp_Mon BETWEEN 4 and 6.
       CONCATENATE 'FY' <RESULT_FIELDS>-fiscper+2(2) 'Q4' INTO
       <RESULT_FIELDS>-/bic/zsp_FYQA.
     elseif <RESULT_FIELDS>-/bic/zsp_Mon BETWEEN 7 and 9.
       CONCATENATE 'FY' <RESULT_FIELDS>-fiscper+2(2) 'Q1' INTO
       <RESULT_FIELDS>-/bic/zsp_FYQA.
     elseif <RESULT_FIELDS>-/bic/zsp_Mon BETWEEN 10 and 12.
       CONCATENATE 'FY' <RESULT_FIELDS>-fiscper+2(2) 'Q2' INTO
       <RESULT_FIELDS>-/bic/zsp_FYQA.
endif.
endloop.
ENDDMETHOD.                    "end_routine
THOD inverse_end_routine.
IMPORTING

Hi,
As suggested by note, you need to put this code in end routine.
Check the syntax , if error go through it and fix syntax (take help of ABAPer if required) and
activate Transformation and DTP.
Thank-You.
Regards,
VB

SAP Short Dumps and PCI Compliance

We've run into an issue with our PCI Compliance audit around being able to see unencrypted credit cards in short dump messages in SAP. Has anyone run into this issue?
Only work around I've got at this point is to restrict all access to short dumps and require many documented signoffs before turning on and off access to a short dump. This is pretty cumbersome, and still leaves a hole in my overall security.
We've managed to purge restricted CC data from our XI logging, and done everything right with encryption, but this short dump issue just doesn't seem to have a solution.
Can anyone help? We're on 6.0.
Thanks!

Hi David,
This is an interesting situation you have described. ABAP short-dumps or run-time errors as they are also known as, are unhandled exceptions during program execution. The conditions that cause such exceptions is unknown or cannot be handled at run-time. To help analyze what went wrong with the said program during execution, it is necessary for the dump to contain all possible information including data values passed between programs when the error occurs. Encryption of restricted data values is a program step in itself. If the dump were to occur after this step then of course it would contain encrypted CC info. Unfortunately in your case it exposes restricted CC info because the dump occurs BEFORE this step.
I don't believe there is a way to prevent this from happening -- for the same reason that the program logic does not know at run-time how to "handle" the exception. If occurrences of such dumps is fairly common in your system, you may want to investigate the likely causes -- for example, missing or incorrect customization. Analyzing the short dumps will probably give you a clue. Your customization team may be able to identify a pre-condition that causes this unhandled exception. If this exception can then be handled (via a program change) that returns a meaningful error instead of a short dump you would be able to close the security hole. This however entails modification to SAP standard code. I don't usually recommend such changes, but given the sensitive nature of your data it may be worth consideration.
I personally advocate restricted access to ST22. The steps you have undertaken to enforce this may be cumbersome despite efforts to keep it simple. I suppose that's the price we pay in administering the system. If you have not already done so, you may also want to ensure that short-dumps that contain restricted CC info are not saved (using the "Keep" feature in ST22) for easy retrieval at a later point in time or they are saved, it be available only to 'restricted eyes'. Short-dumps are normally saved in the system for 7 or 14 days (not sure of exact # of days). The bigger challenge in my opinion is: How do you prevent the restricted info from being viewed by the user who during the course of program/transaction execution encounters the said short dump? No amount of security controls around ST22 will mitigate this risk. The only option that remains is program change (as mentioned above). But to get there you first need to know what causes the exception.
Regards.
Ashutosh

REUSE_ALV_LIST_DISPLAY give short dump beyond 100 columns

Hi,
I have more than 170 columns in my internal table and this gives short dump when it reached 100the column because the structure RS_HEADER which displays column header can only hold 99 columns.
Is there anyway I still use REUSE_ALV_LIST_DISPLAY and overcome the short dump issue.
Regards
Kasi

Although I have not encountered such a case, I would suggest the following: After 99 field, modify the field catalog by setting the excess fields as no_out = abap_true (provided TYPE-POOLS: abap is declared) Then, the user should be limited to a certain number of fields and if he/she wants more fields to be displayed, then he/she should change the layout. I hope that works.

Short dump-internal table size issue

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

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

Short dump due to performance issue

Hi all,
I am facing performance issue in my sandbox. Below is the content of short dump.
Short text
    Unable to fulfil request for 805418 bytes of memory space.
What happened?
    Each transaction requires some main memory space to process
    application data. If the operating system cannot provide any more
    space, the transaction is terminated.
What can you do?
    Try to find out (e.g. by targetted data selection) whether the
    transaction will run with less main memory.
    If there is a temporary bottleneck, execute the transaction again.
    If the error persists, ask your system administrator to check the
    following profile parameters:
    o ztta/roll_area            (1.000.000 - 15.000.000)
           Classic roll area per user and internal mode
           usual amount of roll area per user and internal mode
    o ztta/roll_extension       (10.000.000 - 500.000.000)
           Amount of memory per user in extended memory (EM)
    o abap/heap_area_total      (100.000.000 - 1.500.000.000)
           Amount of memory (malloc) for all users of an application
           server. If several background processes are running on
           one server, temporary bottlenecks may occur.
Pls help me to resolve this issue
Regards,
Kalyani
Edited by: kalyani usa on Jan 9, 2008 9:04 PM

Hi Rob Burbank,
I am pasting the transaction I found in the dump
Transaction......... "SESSION_MANAGER "
Transactions ID..... "4783E5B027A73C1EE10000000A200A17"
Program............. "SAPMSYST"
Screen.............. "SAPMSYST 0500"
Screen line......... 16
Also i am pasting the screenshot of ST02
Nametab (NTAB)                                                                                0
Table definition     99,22     6.799      3.591      62,97    20.000     12.591      62,96       0    8.761
Field definition     99,06    31.563        345       1,15    20.000     13.305      66,53     244    7.420
Short NTAB           99,22     3.625      2.590      86,33     5.000      3.586      71,72       0    1.414
Initial records      52,50     6.625      3.408      56,80     5.000        249       4,98     817    5.568
                                                                                0
program                99,58   300.000      1.212       0,42    75.000     67.561      90,08   7.939   46.575
CUA                    99,08     3.000        211       8,84     1.500      1.375      91,67 23.050      846
Screen                 99,46     4.297      1.842      45,00     2.000      1.816      90,80      81      963
Calendar              100,00       488        401      85,14       200        111      55,50       0       89
OTR                   100,00     4.096      3.281     100,00     2.000      2.000     100,00       0
                                                                                0
Tables                                                                                0
Generic Key          99,69    29.297      2.739       9,87     5.000        177       3,54      57   56.694
Single record        89,24    10.000         63       0,64       500        468      93,60     241 227.134
                                                                                0
Export/import          76,46    50.000     40.980      83,32     2.000                         2.676
Exp./ Imp. SHM         97,82     4.096      3.094      94,27     2.000      1.999      99,95       0
SAP Memory      Curr.Use % CurUse[KB] MaxUse[KB] In Mem[KB] OnDisk[KB] SAPCurCach HitRatio %
Roll area            0,16        432     18.672    131.072    131.072   IDs           98,11
Page area            0,19        496    187.616     65.536    196.608   Statement     95,00
Extended memory      9,89    151.552 1.531.904 1.531.904          0                  0,00
Heap memory                        0          0 1.953.045          0
0,00
Regards,
Kalyani

CJ20N Network creation issue. Short Dump MESSAGE_X; CNPB 011

Hello,
I need your help please.
We have an issue on CJ20N.
We have a short dump MESSAGE_TYPE_X with error message "CNPB 011" in any way we create network on CJ20N (1/ By right click => Network or 2/ Right
click => Copy network or by 3/ drag and drop from templates)
It's noted that:
=> the problem not occurs when we create the network from CN21.
=> We didn't have this problem before.
To avoid the dump and be able access to project, we execute the program that described on note OSS 445323 "Z_DELETE_AFVC_MISSING_AFKO".
After analysis, it turns out that: Records are created on AFVC, AFVV, AFAB, AFVU, JEST, JSTO, etc. BUT NO NETWORK EXISTS IN AFKO for the AUFPL. SO, all is correctly created expect AFKO update.
Can you please help me to see clearly? We don't understand why we have this dump at network creation from CJ20N mainly we didn't have this problem
before.
Thank you in advance for your help,
Amal

Hi Amal,
I would suggest to do the following:
1. Are you getting this DUMP in all of your Clients DEV, Quality and Production?
2. Check if any transport has been moved to Production lately which might have disturbed some settings in PRD Environment if it is happening only in Production Environment.
3. If you are getting DUMP in all of the environments Please raise an OSS with SAP. As what you have described seems to be a Program Bug.
Hope it helps..
Cheers
Sammar

Internal Order status issue Error - Message Class X short dump

Hi All Experts,
I am creating internal order with CRTD status. However when I am trying to post transaction through MIRO , I am getting ABAP short dump mseeage class X. So I changed the CRTD to REL manually and able to solve the error.
But could any expert help me what is the logic behind this CRTD , REL, LKD etc ?
Since I am reading help.sap.com also as well but simple word help will be appreciable !
One more can we,
1 ) Create Internal Order with the REL status directly ?
2 ) If YES where configuration needs to be done
3 ) Will it hamper any business process ?
Exprts guidance will be appreciable.
Regards,
Sharvari Joshi.

Hi,
All Masters,
Eli - Thank you for your answers.
Lawrence - Thank you for simple word that is what I was looking for.
Can anybody tell me how can we create IO directly in LKD status ? Or it is manual acitivity by clicking on Set / Rest button and then check LKD and save. I tried in KOT2_OPA but not no any option found. If any experts can guide for the following configuration would be great.
1 ) Is it possible to create IO with LKD status directly ?
2 ) Where that configuration needs to be done ?
3 ) What is significance of JEST Table relating to Internal Order ?
Exprerts help would be great !
Regards,
Sharvari Joshi.
Edited by: Sharvari Joshi on Dec 3, 2010 11:52 AM

Short dump with decimal issue

Now I want to get total weight of the material as weight * quantity. When I doing this process the program short dump.
If my user setting in su01 is 1,234,567.89 it will work normally, but if I changed my user setting to 1.234.567,89 it will get weight like 6,55 which cause short dump in total weight get. Please help me for solution that no mater user setting is dot or comma it will work successfully. thanks.

I think the problem lies in fact that you are treating this variable as character one (of type c or string ) . This is not correct. You should use only packed numbers (of type p ) for calculation.
The user settings has nothing to do with the calculation. These are purely for displaying data, not for calculating them. So what you need is something like
data: weight type p decimals 2 value '1234567.89',
         quantity type i value 3,
         result(10) type p decimals 2.
result = weight * quantity. "the value stored in variable has form 3703703.67
"only when you display your data it will receive the format of user settings
write: weight, "displayed as 1,234,567.89 or 1.234.567,89 -> depending on the settings
          result.    "displayed as 3,703,703.67 or 3.703.703,67 -> depending on the settings
Regards
Marcin

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.

Custom error message in user exit is giving Short dump

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

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

BCS Release Request Short dump

Hello,
I'm trying to release my costumizing request, that contains the SEM-BCS configuration, although i'm getting a short-dump.
The description is as follows:
Short text
    Access via 'NULL' object reference not possible.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_UG_MD_TR_METHOD_EXPORT=====CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: " ").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
How to correct 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:
    "OBJECTS_OBJREF_NOT_ASSIGNED" " "
    "CL_UG_MD_TR_METHOD_EXPORT=====CP" or "CL_UG_MD_TR_METHOD_EXPORT=====CM003"
    "UGMD_EXTRACT_SID_2"
Information on where terminated
    Termination occurred in the ABAP program "CL_UG_MD_TR_METHOD_EXPORT=====CP" -
     in "UGMD_EXTRACT_SID_2".
    The main program was "RDDM0001 ".
    In the source code you have the termination point in line 62
    of the (Include) program "CL_UG_MD_TR_METHOD_EXPORT=====CM003".
Source Code Extract
Line SourceCde
   32   FIELD-SYMBOLS <lt_table> TYPE INDEX TABLE.
   33   FIELD-SYMBOLS <ld_fsid> TYPE ug_sid.
   34   FIELD-SYMBOLS <ld_vsid> TYPE ug_sid.
   35 * FIELD-SYMBOLS <lt_target> TYPE ANY TABLE.
   36
   37   ASSIGN io_itab->rd_wa->* TO <ls_wa>.
   38   IF i_value_sid IS NOT INITIAL.
   39     ASSIGN COMPONENT i_value_sid
   40            OF STRUCTURE <ls_wa>
   41            TO <ld_vsid>.
   42     CHECK sy-subrc = 0.
   43   ELSE.
   44     CREATE DATA lr_sid.
   45     ASSIGN lr_sid->* TO <ld_vsid>.
   46     CLEAR <ld_vsid>.
   47   ENDIF.
   48
   49   IF NOT i_fieldname_sid IS INITIAL.                  "Start hah160603.1
   50     ASSIGN COMPONENT i_fieldname_sid
   51            OF STRUCTURE <ls_wa>
   52            TO <ld_fsid>.
   53     CHECK sy-subrc = 0.
   54   ELSE.
   55     CALL METHOD ugmd_get_fieldname_to_table
   56       EXPORTING
   57         i_tabname = i_datainfo-tabname
   58       IMPORTING
   59         e_fieldname = ld_fieldname.
   60     lo_fieldname = cl_ug_md_fieldname=>if_ug_md_fieldname~get_instance(
   61       ld_fieldname ).
   62 >>>>>     ld_fieldname_sid_fix = lo_fieldname->ds_data-sid.
   63     ASSIGN ld_fieldname_sid_fix TO <ld_fsid>.
   64   ENDIF.                                                "End hah160603.1
   65
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 1
SY-TABIX 0
SY-DBCNT 0
SY-FDPOS 0
SY-LSIND 1
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY TDR_FULL
SY-UCOMM REFR
SY-TITLE Transport organizer: ordens
SY-MSGTY I
SY-MSGID FINB_TR
SY-MSGNO 009
SY-MSGV1 &
SY-MSGV2 &
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080904
SY-UZEIT 200112
SY-XPROG SAPLSYST
SY-XFORM SYSTEM_HOOK_OPEN_DATASET
If someone have gone trough a similar experience, or have any tip of how to solve this issue, i'd apreciate a comment.
Will award points for valuable help.
Thank you

Hi Ricardo,
You tried to transport the BCS' configuration, right?
If in the request was the full set of settings from the start of the project, the it will definitely fail.
There are some restrictions in BCS transport. See, for example the OSS Note #627924 - 'Restrictions with transport in BW-based SEM-BCS'. It particularly says:
"For the initial system setup, and after substantial changes in the data model, you should transport the Customizing by means of manually created transport requests. We advise you not to use the automatic recording of all Customizing settings during the first implementation phase in the development system and not to use this request for the structure of the test and productive systems.
During the transport of a new consolidation area, the following settings should be transported in the following sequence:
1. Data basis
2. Consolidation area
3. Special versions
After the import of the data basis and the consolidation area, these settings should be checked in the target system. In particular, the RFC destination, the InfoCubes and ODS objects, as well as the InfoObjects. Note that RFC destinations, InfoCubes, ODS objects, virtual cubes and InfoObjects cannot be transported from the consolidation workbench with the transport functions. For instance, you have to transport and activate the InfoCubes and InfoObjects using the BW."
I usually transport the BCS setting in a little transport requests in this order:
- all BW objects and settings
- data basis (with source DB)
- cons area
- special versions
- versions
- master data
...etc.
Hope this helps.

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 Dump issue

Similar Messages

Maybe you are looking for