SHORT DUMP due to STORAGE_PARAMETERS_WRONG_SET in ALV

Hello All,
There is an internal table containing more than 200,000 thousand records.
when this is passed to ALV grid for display, the program terminates with the exception STORAGE_PARAMETERS_WRONG_SET
I was wondering if there is a way to prevent the program from terminating.
Are there any system settings that can be changed/checked?
(Its an Unix OS).
Any help is welcome.
Many thanks!
Vinay

This is what SAP documentation says:
Set the system profile parameters
- abap/heap_area_dia
- abap/heap_area_nondia
to a maximum value. Then reduce the value by 10.000.000 to be on the
safe side.
Then restart the SAP System.
When the program was running, it was established that more
memory was needed than the operating system is able to provide savely
To avoid a system crash, you must prevent this
situation.
The program had already requested &P1 bytes from the operating
system with 'malloc' when the operating system reported after a
further memory request that there was no more memory space
available.

Similar Messages

Getting Short dump due to large amount of data

Hi experts,
When we are running RALM_ME_MEASP_FULL_DOWNLOAD_SD program, every time we are getting Short dump due to large amount of data.
please suggest how to run this program without short dump.
Thanks & Regards
Prashant Gupta

Hi,
you do run the wrong APP I guess. The service you are running is for MAM20. If you are interested in MAM30 and MAM25, please use the correct service.
If you have a look for
*FULL_DOWNLOAD_SD
You find them all. Use the ones without the RALM in front - then the timeout should be solved as well. Bside that there is a great guid available that helps as well to solve some issues around server driven replication:
[MAM SERVER DRIVEN SETUP GUIDE|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/818ac119-0b01-0010-ba8b-b6e3f3490a63?quicklink=index&overridelayout=true]
Hope that helps to solve yourt issue.
Regards,
Oliver

Short Dump while scrolling on the ALV (GETWA_NOT_ASSIGNED)

Hi All,
I have an interactive ALV list, After the user double click on the list line item,
the list control goes to top of the list.
When i want to scroll for further interaction, I am getting a Short dump GETWA_NOT_ASSIGNED.
Please advice
Solomon

Hi
Please find the ALV code
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_callback_program       = hf_repid
      i_callback_user_command = 'USER_COMMAND'
      i_callback_pf_status_set = 'SET_PF_STATUS'
      it_fieldcat              = int_fieldcat[]
      it_sort                  = int_sort[]
      is_layout                = fs_layout
      i_save                   = 'A'
      is_variant               = alv_variant
      it_events                = int_events[]
    TABLES
      t_outtab                 = i_bsid
    EXCEPTIONS
      program_error            = 1
      OTHERS                   = 2.
ENDFORM.                               " write_alv_report
FORM user_command *
FORM user_command USING ucomm LIKE sy-ucomm
selfield TYPE slis_selfield.
IF selfield-tabindex GE 1.
    check sy-ucomm <> 'POST'.
    READ TABLE i_bsid into i_bsid_alv INDEX selfield-tabindex.
    CASE I_BSID-CHECK.
      WHEN SPACE.
        I_BSID-CHECK = 'X'.
      WHEN OTHERS.
        I_BSID-CHECK = ''.
    ENDCASE.
    MODIFY I_BSID TRANSPORTING CHECK WHERE matchkey = i_bsid_alv-matchkey.
ENDIF.
selfield-refresh = 'X'.
*CLEAR selfield.
ENDFORM.                    "user_command
FORM SET_PF_STATUS *
FORM set_pf_status USING extab TYPE slis_t_extab.
data : lv_answer(1) TYPE c.
SET PF-STATUS 'S200'.
IF SY-UCOMM = 'POST'.
    I_BSID_ALV1[] = I_BSID[].
    DELETE I_BSID_ALV1 WHERE CHECK = SPACE.
    CLEAR I_BSID[].
    I_BSID[] = I_BSID_ALV1[].
ENDIF.
2. when I double click on the ALV list line item, after the line is selected the control goes to the top of the list.
I have already setup the ALV menu bar.

Short dump due termination in the program SAPLSNR3

Hi Experts,
While running an IP I am getting short dump, and error analysis says
An ASSIGN statement in the program "SAPLSNR3" contained a field symbol with
length 0. This is not possible. length 0.This is not possible.
can any one exlain why the IP is going for short dump,rectify the error and make the IP to run sucessful.
Regards,
Siddhardh

Hi Suresh,
Your dump is occuring due to database limit of sql statment (Native SQL) that is generated from your abap sql. The range is killing him (as you already notice).
The thread bellow have some info about this, but the solution can't be applyed to you:
To update 1 field of ztable(60 fields) for 2000 records in minimum DB hit
Maybe you can build some logic to reduce the value of two ranges (also concatenating them). Anyway, due to amount of lines involved (24.500 lines).... I don't think it is possible.
One option is filter the result on ABAP, after your SQL w/o the ranges you may try:
DELETE FROM TABLE i_glpct2
WHERE NOT ( racct IN r_profloss OR racct IN r_balsheet ).
This can raise a performance problem if the number of returned rows from database is to high.
Another option is change your database access. Where the values of the two ranges came from ? database ? If they came from database try to use INNER JOIN, this will solve the problem w/o performance problem.
Best Regards, Fernando Da Ró

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

Short Dump due to TIME_OUT Error

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

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

Short dump due to conversion error on screen

Hello all,
I have designed one screen, and throwing error message if perticular filed is blank as (message e002(z2)). If i keep the filed blank system is throwing error message but giving short dump because of 'Conversion error' .
Error analysis : 'The program has been interrupted and cannot resume. |
Program "SAPMZTIMECOLLECT_NEW" attempted to display fields on screen 0101.
| An error occurred during the conversion of this data. '
Please, could you help to understand why system is giving short dump.
Thanks in advance..!!

Solved for me.
If we don't have value for the field which we are passing it to tablecontrol, then declare the variable with the same type and assigned space for the same and submit it to table control output. then the error is not coming.
Ex: If we dont have the value for the table control field (KOSTL), then declare one constant K_KOSTL LIK below,
DATA:K_KOSTL TYPE KOSTL.
K_KOSTL = ' '.
IF the value of table control field is initial, then pass K_KOSTL to it.
This what I have done.
Regards
Ramesh.

Short dump due to Memory Space

Hi Experts,
I have an internal table whose width is 3576 characters. My selection criteria is selecting approximately 1 million record from the database table.
Out of the 3576 characters, I m not even filling 150 characters a row using selection fields.
The short dump is as follows:
Error analysis
    The internal table "\PROGRAM=ZPMWO_DSR_RECONCILIATION\FORM=RECONCILIATION\DATA=
    LT_VIQMEL_I" could not be further extended. To enable
    error handling, the table had to be delete before this log was written.
    As a result, the table is displayed further down or, if you branch to
    the ABAP Debugger, with 0 rows.
    At the time of the termination, the following data was determined for
    the relevant internal table:
    Memory location: "Session memory"
    Row width: 3576
    Number of rows: 1035860
    Allocated rows: 1035860
    Newly requested rows: 4 (in 1 blocks)
How to correct this?? I mean how do i increase the memory space required for this process??

Hi,
Check there is not an endless loop which is appending data in the internal table.
Regards,
Ankur Parab

Short dump when trying to download alv( reuse_alv_grid data) into excel

Hi SAPAll.
here i have got one alv report ,when executing this alv report it displays in correct way but the only problem is when i click on the icon(local file) which exists at standard tool bar at the top to dowbload into local excel file it is raising the runtime error as
The current statement requires a character-type data object.
at happened?
Error in the ABAP Application Program
The current ABAP program "SAPLKKBL" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
ror analysis
At the statment
"STRLEN( obj )..."
, only character-type data objects are supported at the argument
position "obj".
In this particular case, the operand "obj" has the non-charcter-type type
"P".
igger Location of Runtime Error
Program SAPLKKBL
Include LKKBLF99
Row 3.948
Module type (FORM)
Module Name GEN_FIELD_OUT2
Line SourceCde
3923 * Bei NUMC führende '0' und ' ' nicht berücksichtigen
3924 elseif gs_fc-tech_form = 6.
3925 write to gs_out-hlpchar no-zero left-justified.
3926 if gs_fc-just = 'R'.
3927 condense gs_out-hlpchar.
3928 endif.
3929 gs_out-hlplen = strlen( gs_out-hlpchar ).
3930 elseif gs_fc-tech_form = 11. "INS TECH11
3931 * Min. Ausgabelänge für ein Datum ist immer 8
3932 if gs_fc-datatype = 'DATS'. "INS TECH11
3933 gs_out-hlplen = 8. "INS TECH11
3934 * Min. Ausgabelänge für eine Uhrzeit ist immer 6
3935 elseif gs_fc-datatype = 'TIMS'. "INS TECH11
3936 gs_out-hlplen = 6. "INS TECH11
3937 endif. "INS TECH11
3938 elseif gs_fc-tech_form = 1 or gs_fc-tech_form = 90.
3939 * Überführung int. in ext. Format via Konvertierungsexit
3940 if not gs_fc-convexit is initial or "INS TECH11
3941 not gs_fc-inttype ca 'CN'.
3942 * elseif not gs_fc-convexit is initial. "DEL TECH11
please respond at ur time

Hi,
Verify your field_cat, because the element (column) with value (type P) may be defined with the parameter inttype = 'C' or inttype = 'N'.
You have to change to inttype = 'P' .
Best regards,
Leandro Mengue

Short dump when trying to download alv into excel

Hi SAPAll.
here i have got one alv report ,when executing this alv report it displays in correct way but the only problem is when i click on the icon(local file) which exists at standard tool bar at the top to dowbload into local excel file it is raising the runtime error as
The current statement requires a character-type data object.
at happened?
Error in the ABAP Application Program
The current ABAP program "SAPLKKBL" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
ror analysis
At the statment
       "STRLEN( obj )..."
, only character-type data objects are supported at the argument
position "obj".
In this particular case, the operand "obj" has the non-charcter-type type
"P".
igger Location of Runtime Error
Program                                 SAPLKKBL
Include                                 LKKBLF99
Row                                     3.948
Module type                             (FORM)
Module Name                             GEN_FIELD_OUT2
Line SourceCde
3923 * Bei NUMC führende '0' und ' ' nicht berücksichtigen
3924   elseif gs_fc-tech_form = 6.
3925     write to gs_out-hlpchar no-zero left-justified.
3926     if gs_fc-just = 'R'.
3927       condense gs_out-hlpchar.
3928     endif.
3929     gs_out-hlplen = strlen( gs_out-hlpchar ).
3930   elseif gs_fc-tech_form = 11.                              "INS TECH11
3931 *   Min. Ausgabelänge für ein Datum ist immer 8
3932     if gs_fc-datatype = 'DATS'.                             "INS TECH11
3933       gs_out-hlplen = 8.                                    "INS TECH11
3934 *    Min. Ausgabelänge für eine Uhrzeit ist immer 6
3935     elseif gs_fc-datatype = 'TIMS'.                         "INS TECH11
3936       gs_out-hlplen = 6.                                    "INS TECH11
3937     endif.                                                  "INS TECH11
3938   elseif gs_fc-tech_form = 1 or gs_fc-tech_form = 90.
3939 *   Überführung int. in ext. Format via Konvertierungsexit
3940     if not gs_fc-convexit is initial or                     "INS TECH11
3941        not gs_fc-inttype ca 'CN'.
3942 *   elseif not gs_fc-convexit is initial.            "DEL TECH11
will be waiting for quick response please respond at your discretion.
regards.
Varma
Edited by: Thomas Zloch on Mar 11, 2010 11:48 AM

hi suhas .
the folliwing below is the code for alv and i had used 2 different structures for populating the data into alv
FORM fieldcat_init USING    p_fieldcat TYPE slis_t_fieldcat_alv.
DATA: ls_fieldcat TYPE slis_fieldcat_alv.
CLEAR ls_fieldcat.
ls_fieldcat-fieldname   = 'ORDER'.
ls_fieldcat-ref_tabname = 'st_proc_out'.
ls_fieldcat-key         = 'X'.
ls_fieldcat-seltext_s   = 'ORDER NUMBER'.
ls_fieldcat-seltext_m   = 'ORDER NUMBER'.
ls_fieldcat-seltext_l   = 'ORDER NUMBER'.
APPEND ls_fieldcat TO p_fieldcat.
CLEAR ls_fieldcat.
ls_fieldcat-fieldname   = 'P_ORDER'.
ls_fieldcat-ref_tabname = 'st_proc_out'.
ls_fieldcat-key         = 'X'.
ls_fieldcat-seltext_s   = 'P.O.NUMBER'.
ls_fieldcat-seltext_m   = 'P.O.NUMBER'.
ls_fieldcat-seltext_l   = 'P.O.NUMBER'.
APPEND ls_fieldcat TO p_fieldcat.
CLEAR ls_fieldcat.
ls_fieldcat-fieldname   ='LINE'.
ls_fieldcat-ref_tabname = 'st_proc_out2'.
ls_fieldcat-key         = 'X'.
ls_fieldcat-seltext_s   = 'Line Number'.
ls_fieldcat-seltext_m   = 'Line Number'.
ls_fieldcat-seltext_l   = 'Line Number'.
APPEND ls_fieldcat TO p_fieldcat.
CLEAR ls_fieldcat.
ls_fieldcat-fieldname   ='MATNO'.
ls_fieldcat-ref_tabname = 'st_proc_out2'.
ls_fieldcat-key         = 'X'.
ls_fieldcat-seltext_s   = 'Mat.Number'.
ls_fieldcat-seltext_m   = 'Mat.Number'.
ls_fieldcat-seltext_l   = 'Mat.Number'.
APPEND ls_fieldcat TO p_fieldcat.
CLEAR ls_fieldcat.
ls_fieldcat-fieldname   ='MATERIAL'.
ls_fieldcat-ref_tabname = 'st_proc_out2'.
ls_fieldcat-key         = 'X'.
ls_fieldcat-seltext_s   = 'Mat Descrption'.
ls_fieldcat-seltext_m   = 'Mat Descrption'.
ls_fieldcat-seltext_l   = 'Mat Descrption'.
APPEND ls_fieldcat TO p_fieldcat .
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_callback_program = 'YSDRO024C1'
      i_grid_title       = 'EXPORT ORDER REPORT'
      is_layout          = alv_layout
      it_fieldcat        = alv_fieldcat
      i_save             = 'A'
    TABLES
      t_outtab           = i_output
    EXCEPTIONS
      program_error      = 1
      OTHERS             = 2.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
PERFORM proc_print.
FORM proc_print .
DATA: ls_fieldcat TYPE slis_fieldcat_alv.
CLEAR ls_fieldcat.
ls_fieldcat-col_pos     = '1'.
ls_fieldcat-fieldname   = 'ORDER'.
ls_fieldcat-key         = 'X'.
ls_fieldcat-seltext_m   = 'ORDER NUMBER'.
ls_fieldcat-ddictxt     = 'M'.
APPEND ls_fieldcat TO alv_fieldcat.
CLEAR ls_fieldcat.
ls_fieldcat-col_pos     = '2'.
ls_fieldcat-fieldname   = 'P_ORDER'.
ls_fieldcat-key         = 'X'.
ls_fieldcat-seltext_m   = 'PO NUMBER'.
ls_fieldcat-ddictxt     = 'M'.
APPEND ls_fieldcat TO alv_fieldcat.
regards,
Varma

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,

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 while copying Org structure from ERP to CRM

Hello Experts:
We are trying to copy the Org structure from ECC to CRM.
We have a standard transaction 'CRMC_R3_ORG_GENERATE' to copy the the org structure from ECC or the IMG path:
SPRO->CRM->Master Data->Organization Management->Data Transfer->Coppy ECC Sales Structure
We have a multiple assignment scenario where each sales groups are assigned to multiple sales offices and likewise,each sales office is assigned to multiple sales org unit in ECC.
This can be achieved by turning on the enhanced version.
In our current business,even though the sales offices and groups are created,but are not having relavance in the business,hence while running in the sandbox system, we ran the program to copy the structures in the standard mode(default) and we could copy it without issues and create the org units for every entity in CRM based on how the number ranges are defined.
What happens when enhanced version switch is turned on ::
While we turn the mode to enhanced version, The system automatically::
- enhances the Function tab page in the ppoma_crm transaction to include a grid table, in which you maintain multiple assignments of organizational units
- generates an extra dialog box to the Organization tab page in business transactions for you to select the relevant assignment path for the organizational unit
- adapts the consistency check in business transactions to take into account organizational units that have been multiple assigned
Risk factor :
Once you have switched to the enhanced backend integration version of the organizational model you cannot return to the standard backend integration version. The system will also automatically make changes to the organizational model version in CRM Mobile Sales.
Also this structure will happen across all the clients in the system,so unfortunately cannot try in a sandbox client also of the new environment.
We are building our development box,so while running the above step in standard mode,the program gives a short dump due to long execution time even though we have the same amount of data as in our prototype system.
Also, we increased the idle time value to a very high value.
When I approached SAP OSS,I was told that it is due to the multiple assignment scenario,hence we need to switch to enhanced version in CRM before we run the copy program ( CRMC_ORG_R3_GENERATE )
I am not quite sure if the mismatch of the scenarios between CRM and ECC could be causing this short dump as we could run it in standard mode in our prototype/sandbox environment without issues even with the same data volume as in the new development system .
I am looking for help from all the experts if they have come across similar issue and your recommendations/feedback if this can be corrected.
Appreciate your guidance/recommendation on this issue.
thanks!!

In CRM Best Practices Building block C05 is the step by step description how to replicate Org. structure and some of employee's master data.
Follow link - http://help.sap.com/bp_crmv12007/CRM_DE/BBLibrary/html/C05_EN_DE.htm

Short Dump when downloading to EXCEL from ALV

Hi,
I have an ALV grid display program. The data in the grid is displayed correctly. But when trying to download the data to excel it gives a short dump.
Assignment error: Overwriting a protected field.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLKKBL" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
Some times it allows to download the data, but sometimes it gives short dump.
Thanks,
Deepthi

This is my part of the code:
i_fieldcat-key     = gc_x.
i_fieldcat-no_zero = gc_x.
i_fieldcat-fix_column = 'X'.
i_fieldcat-hotspot = gc_x.
perform bild_fieldcat using
    '' 'AUFNR' 'GT_REPORT ' ' ' 'CAUFV' ' ' 'C' '12' ' '.
perform bild_fieldcat using
    '' 'DISGR' 'GT_REPORT ' ' ' 'MARC' ' ' 'C' '4' ' '.
perform bild_fieldcat using
    '' 'AUART' 'GT_REPORT ' ' ' 'CAUFV' ' ' 'C' '04' ' '.
perform bild_fieldcat using
    '' 'DISPO' 'GT_REPORT ' ' ' 'CAUFV' ' ' 'C' '06' ' '.
i_fieldcat-no_zero = gc_x.
perform bild_fieldcat using
    '' 'MATNR' 'GT_REPORT ' ' ' 'MARA' ' ' 'C' '18' ' '.
i_fieldcat-no_zero = gc_x.
perform bild_fieldcat using
    '' 'CHARG' 'GT_REPORT ' ' ' 'MDFA' ' ' 'C' '14' ' ' .
*begin insert RCHALASA
i_fieldcat-no_zero = gc_x.
i_fieldcat-fix_column = 'X'.
perform bild_fieldcat using
    '' 'FTRMI' 'GT_REPORT ' ' ' 'CAUFV' ' ' 'D' '08' ' '.
*end insert
i_fieldcat-no_zero = gc_x.
i_fieldcat-fix_column = 'X'.
perform bild_fieldcat using
    '' 'GLTRP' 'GT_REPORT ' ' ' 'CAUFV' ' ' 'D' '10' ' '.
i_fieldcat-no_zero = gc_x.
perform bild_fieldcat using
    '' 'GLTRS' 'GT_REPORT' ' ' 'CAUFV' ' ' 'D' '10' ' '.
perform bild_fieldcat using
    '' 'GSTRP' 'GT_REPORT' ' ' 'CAUFV' ' ' 'D' '10' ' '.
perform bild_fieldcat using
    '' 'AGE' 'GT_REPORT' ' ' ' ' 'Age' 'C' '08' ' '.
i_fieldcat-no_zero = gc_x.
i_fieldcat-do_sum = gc_x.
i_fieldcat-fix_column = 'X'.
perform assign_alv_qty_format.
perform bild_fieldcat using
    '' 'GAMNG' 'GT_REPORT' ' ' ' ' 'Order Qty' 'QUAN' '09' ' '.
perform bild_fieldcat using
    '' 'STK_PROD_FLAG' 'GT_REPORT' ' '   ' ' 'Stk/Prod' 'C' '06' ' '.
i_fieldcat-no_zero = gc_x.
i_fieldcat-do_sum = gc_x.
i_fieldcat-fix_column = 'X'.
perform assign_alv_qty_format.
perform bild_fieldcat using
    '' 'IGMNG' 'GT_REPORT' ' ' ' ' 'Order Yield Qty' 'QUAN' '11' ' '.
i_fieldcat-no_zero = gc_x.
i_fieldcat-do_sum = gc_x.
i_fieldcat-fix_column = 'X'.
perform assign_alv_qty_format.
perform bild_fieldcat using
    '' 'IASMG' 'GT_REPORT' ' ' ' ' 'Order Scrap Qty' 'QUAN' '11' ' '.
**begin insert RCHALASA
perform bild_fieldcat using
     '' 'YIELD_PER' 'GT_REPORT' ' ' ' ' 'Yield' 'C' '05' ' '.
**end insert
DATA: col_pos like sy-colno.
col_pos = '17'.
loop at gt_oper.
    gv_tabix = sy-tabix.
    i_fieldcat-no_zero = gc_x.
    i_fieldcat-do_sum = gc_x.
    i_fieldcat-fix_column = 'X'.
   col_pos = col_pos + 1.
    perform assign_alv_qty_format.
    gv_yield6(03) = gt_oper-vornr1(03).
*begin insert RCHALASA
    move gt_oper-ltxa1 to gv_text.
translate gv_text to upper case.
gv_text = gv_yield.
*end insert
    gv_tabixn = gv_tabix.
    gv_yield+6(03) = gv_tabixn.
    gv_fieldname = gv_yield.
    translate gv_fieldname to upper case.
    perform bild_fieldcat using
     '' gv_fieldname 'GT_REPORT' ' ' ' ' gv_text 'QUAN' '04' ' '.
   perform assign_alv_qty_format.
gv_scrap6(03) = gt_oper-vornr1(03).
select single
         grdtx
         from trugt
         into gv_text1
         where
         grund = gt_oper-vornr
         and werks in s_werks.
   gv_text = gv_scrap.
   i_fieldcat-no_zero = gc_x.
   gv_tabixn = gv_tabix.
gv_scrap+6(03) = gv_tabixn.
   gv_fieldname = gv_scrap.
   translate gv_fieldname to upper case.
   perform bild_fieldcat using
     gv_fieldname 'GT_REPORT' ' ' gv_text1 'X' 'QUAN' '08' ' '.
   clear gv_text1.
endloop. " GT_OPER
DATA: count type c.
DESCRIBE table gt_grund lines count.
loop at gt_grund into gl_grund.
    gv_tabix = sy-tabix.
    i_fieldcat-no_zero = gc_x.
    i_fieldcat-do_sum = gc_x.
    i_fieldcat-fix_column = 'X'.
    perform assign_alv_qty_format.
    if gl_grund-grund is initial.
      gl_grund = 'NONE'.
      gv_text = gl_grund.
    else.
       gv_text = gl_grund-grdtx.
    endif.
    gv_tabixn = gv_tabix.
    gv_scrap_code+11(03) = gv_tabixn.
    gv_fieldname = gv_scrap_code.
    translate gv_fieldname to upper case.
   col_pos = col_pos + 1.
    perform bild_fieldcat using
      '' gv_fieldname 'GT_REPORT' 'XMNGA' 'AFRU' gv_text 'QUAN' '12' ' ' .
endloop. " GT_OPER
gb_layout-zebra = 'X'.
gb_print-no_print_listinfos = 'X'.
gb_variant-variant = p_varia.
perform create_events using gt_events[].
call function 'SAPGUI_PROGRESS_INDICATOR'
    EXPORTING
      text = 'Reading SAP Records.......'(600).
call function 'REUSE_ALV_GRID_DISPLAY'
       exporting
            i_callback_program       = gv_repid
            i_callback_top_of_page   = 'TOP_OF_PAGE'
           i_callback_pf_status_set = 'SET_STATUS'
            i_callback_user_command = 'CALL_UP_SAP_TRANS'
            it_fieldcat              = i_fieldcat[]
            is_layout                = gb_layout
            i_grid_title             = gb_title
            i_default                = 'X'
            i_save                   = 'X'
            is_variant               = gb_variant
            is_print                 = gb_print
            it_events                = gt_events[]
       tables
            t_outtab                 = gt_report
       exceptions
            program_error            = 1
            others                   = 2.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
             with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
***********ALV SUBROUTINE**************
TYPE-POOLS: slis.
DATA: gv_repid            LIKE sy-repid.
DATA: i_fieldcat          TYPE slis_t_fieldcat_alv WITH HEADER LINE.
DATA: gb_layout           TYPE slis_layout_alv.
DATA: gb_selfield         TYPE slis_selfield.
DATA: gb_print            TYPE slis_print_alv.
DATA: i_sort              TYPE slis_t_sortinfo_alv WITH HEADER LINE.
DATA: gv_keyinfo          TYPE SLIS_KEYINFO_ALV.
DATA: gb_variant          LIKE disvariant,
      gb_def_variant      LIKE disvariant.
DATA: gb_title(70).
DATA: gt_events           TYPE slis_t_event,
      gt_sort             TYPE SLIS_T_SORTINFO_ALV,
      gt_list_top_of_page TYPE slis_t_listheader,
      g_status_set        TYPE slis_formname VALUE 'PF_STATUS_SET',
      g_user_command      TYPE slis_formname VALUE 'USER_COMMAND',
      g_top_of_page       TYPE slis_formname VALUE 'TOP_OF_PAGE',
      g_end_of_page       TYPE slis_formname VALUE 'END_OF_PAGE',
      g_top_of_list       TYPE slis_formname VALUE 'TOP_OF_LIST',
      g_end_of_list       TYPE slis_formname VALUE 'END_OF_LIST'.
DATA: it_event_exit TYPE slis_t_event_exit WITH HEADER LINE.
*--- Rotinas ---
FORM alv_init.
CLEAR: gb_variant.
gv_repid = sy-repid.
gb_variant-report = gv_repid.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
       EXPORTING
            i_save     = 'A'
       CHANGING
            cs_variant = gb_variant
       EXCEPTIONS
            not_found = 2.
IF sy-subrc = 0.
    p_varia = gb_variant-variant.
ENDIF.
ENDFORM.                    " ALV_INIT
FORM alv_f4.
gb_variant-report = gv_repid.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
       EXPORTING
            is_variant = gb_variant
            i_save     = 'A'
       IMPORTING
            es_variant = gb_variant
       EXCEPTIONS
            not_found = 2.
IF sy-subrc = 2.
    MESSAGE ID sy-msgid TYPE 'S' NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
    p_varia = gb_variant-variant.
ENDIF.
ENDFORM.                                                    " ALV_F4
FORM bild_fieldcat USING x_pos x_field x_tab x_reffld x_ref x_text x_type x_tam x_sym.
i_fieldcat-col_pos       = x_pos.
i_fieldcat-fieldname     = x_field.
i_fieldcat-tabname       = x_tab.
i_fieldcat-ref_fieldname = x_reffld.
i_fieldcat-ref_tabname   = x_ref.
i_fieldcat-seltext_l     = x_text.
i_fieldcat-seltext_m     = x_text.
i_fieldcat-seltext_s     = x_text.
i_fieldcat-ddictxt = 'M'   .
i_fieldcat-inttype       = x_type.
i_fieldcat-outputlen     = x_tam.
i_fieldcat-symbol        = x_sym.
APPEND i_fieldcat.
CLEAR i_fieldcat.
ENDFORM.                    " BILD_FIELDCAT
FORM create_events USING rt_events TYPE slis_t_event.
DATA: ls_event TYPE slis_alv_event.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
       EXPORTING
            i_list_type = 0
       IMPORTING
            et_events   = rt_events.
READ TABLE rt_events WITH KEY name = slis_ev_top_of_page
                           INTO ls_event.
IF sy-subrc = 0.
    MOVE g_top_of_page TO ls_event-form.
    APPEND ls_event TO rt_events.
ENDIF.
ENDFORM.                    "

Short dump SAPLSLVC_FULLSCREEN in ALV mode

Hi all
I encountered a short dump in production after i load a text file in my customised program. I did not encountered such error in DEV and UAT. This dump occurs when i add or remove the columns in ALV mode.
Runtime Error          PERFORM_NOT_FOUND
Exception              CX_SY_DYN_CALL_ILLEGAL_FORM
       Occurred on     22.05.2008 at   15:02:44
Call (PERFORM) to a non-existent routine.
What happened?
The current program attempted to call an externally defined routine
that does not exist.
Error in ABAP application program.
The current ABAP program "SAPLSLVC_FULLSCREEN" had to be terminated because one
of the
statements could not be executed.
This is probably due to an error in the ABAP program.
The current ABAP program had to be terminated because the
ABAP processor detected an internal system error.
The current ABAP program "SAPLSLVC_FULLSCREEN" had to be terminated because the
ABAP
processor discovered an invalid system state.
Can anyone kindly advice? Thanks.

** WA-NAME = 'TOP_OF_PAGE'.             "'SLIS_EV_TOP_OF_PAGE'.
** WA-FORM = 'TOPOFPAGE'.
** APPEND WA TO T_EVENTS.
** WA-NAME = 'END_OF_PAGE'.
** WA-FORM = 'ENDOFPAGE'.
** APPEND WA TO T_EVENTS.
** WA-NAME = 'END_OF_LIST'.
** WA-FORM = 'ENDOFLIST'.
** APPEND WA TO T_EVENTS.
please comment like this code in your code..

SHORT DUMP due to STORAGE_PARAMETERS_WRONG_SET in ALV

Similar Messages

Maybe you are looking for