Dump error in smartforms

HI Experts,
I have one doubts in smartforms, i m using two SELECT SINGLE statement first SELECT SINGLE is working properly, i m getting employee name but second SELECT SINGLE is provide dump error,
i m providing below my se38 code for ur help. Plz help me as soon as possible.
TABLES: PERNR, PA0000, PA0001, PA0006.
*INFOTYPES: 0000, 0001, 0006.
DATA: V_FORMNAME TYPE TDSFNAME VALUE 'ZWARN_LETTER',
      v_fmname type rs38l_fnam.
SELECTION-SCREEN BEGIN OF BLOCK SAN WITH FRAME TITLE Title.
PARAMETERS: EMPNO TYPE PA0000-PERNR OBLIGATORY.
SELECTION-SCREEN END OF BLOCK SAN.
DATA: ENAME LIKE PA0001-ENAME,         " EMPLOYEE NAME.
      STRAS LIKE PA0006-STRAS,
      ORT01 LIKE PA0006-ORT01,
      ORT02 LIKE PA0006-ORT02,
      PSTLZ LIKE PA0006-PSTLZ,
      LOCAT LIKE PA0006-LOCAT.
DATA: BEGIN OF ITAB OCCURS 0,
      ENAME LIKE PA0001-ENAME,         " EMPLOYEE NAME.
      STRAS LIKE PA0006-STRAS,
      ORT01 LIKE PA0006-ORT01,
      ORT02 LIKE PA0006-ORT02,
      PSTLZ LIKE PA0006-PSTLZ,
      LOCAT LIKE PA0006-LOCAT.
DATA: END OF ITAB.
*SELECT SINGLE PERNR INTO ITAB-EMPNO FROM PA0000 WHERE PERNR = EMPNO.
SELECT SINGLE ENAME INTO ITAB-ENAME FROM PA0001 WHERE PERNR = EMPNO.
   SELECT SINGLE STRAS FROM PA0006 INTO (ITAB-STRAS) WHERE PERNR = EMPNO .
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
EXPORTING
    formname                = v_formname
IMPORTING
   FM_NAME                  = v_fmname
EXCEPTIONS
NO_FORM                  = 1
NO_FUNCTION_MODULE       = 2
OTHERS                   = 3
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION V_FMNAME
     EXPORTING
          ENAME = ITAB-ENAME.
          STRAS = ITAB-STRAS.
        ORT01 = ITAB-ORT01.
        ORT02 = ITAB-ORT02.
        PSTLZ = ITAB-PSTLZ.
        LOCAT = ITAB-LOCAT.
Regards,
Swapnika

HI,
In FM
CALL FUNCTION V_FMNAME
EXPORTING
ENAME = ITAB-ENAME.
STRAS = ITAB-STRAS.
ORT01 = ITAB-ORT01.
ORT02 = ITAB-ORT02.
PSTLZ = ITAB-PSTLZ.
LOCAT = ITAB-LOCAT.
Here ITAB is the Internal table. So we can't directly pass internal table values.
Try like this,
just change the declarations.
data : itab-ename type table value,
itab-stras type table value.
Select statements.
call FM

Similar Messages

Dump error in smartforms , please help me urgent

Hi,
i have created a smartform with two pages in it , i was not able to create the window in the second page it was showing me a dump error but i manage to copy the main window of first page in to second page it was working fine but if i delete anything in it , it was reflecting in first page , then i managed to reduce the size of the main window and add a secondayry window , as the content of the second page must flow to pages . i need to create a main window , it is aagin throwing a dump error , plsease help me in sloving in this , thanks
srihar

Hi,
create folder in main area in main wondow and keep all the rows of table in folder.
the go to output options of folder and tick check box Page protection.
Now u can reduce the size of main window in second page .it will not get any short dump.
regards,
Sunil.K

Regarding dump error in smartforms

hi experts,
               my one driver program along with smartforms is working fine in the development server after transportation to production server it is showing dump error :::
the error is:
Function module " " not found.
What happened?
The function module " " was called, but cannot be
    found in the Function Library.
Error in ABAP application program.
The current ABAP program "ZSD_DELIVERY_ORDER_DRIVER_PREP" had to be terminated
     because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
     termination messages, especially those beyond their normal deletion
    date.
is especially useful if you want to keep a particular message.
Error analysis
An exception occurred. This exception will be dealt with in more detail
    below. The exception, assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
     not caught, which
led to a runtime error. The reason for this exception is:
    The program "ZSD_DELIVERY_ORDER_DRIVER_PREP" contains a CALL FUNCTION
     statement. The name
of the function module to be called is " ".
No function module exists with the name " ".
    All function modules are stored in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Particular attention should be paid
       to upper/lower case and underscores ("_")
    b) Transport error
c) If an enqueue/dequeue module has been used, the lock object
       may not have been activated (ABAP Dictionary)
       may not have been activated (ABAP Dictionary).
i have checked in the production server but i m not finding <b>" "</b> this thing in the program ..plz help me to solve this.

Hi Ravi,
Can you show me the code where you have called the smart form in driver program.Becaus the FM generated in Development server may differ from the FM generated in Production server.Make sure u r passing the FM which is generated from the function module SSF_FUNCTION_MODULE_NAME.

Dump error while creating a new page in smartforms URGENT pls!!!

while creating a new page it is showing me a dump error , that the superior program execption was not intercepted , i have even given the next page field also correctly, i have attached a mainwindow to that page and a text element to that . .
thanks
sridhar

Hi Deena,
This error:
"[2012-07-10T14:50:30.005+05:30] [wls_ods1] [ERROR] [] [oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000JXkC9dU3FClqwsJb6G1FyhO000003D,0] [APP: odsm#11.1.1.2.0] Server Exception during PPR, #7[[
javax.servlet.ServletException: Could not initialize class com.octetstring.vde.admin.services.client.VDEAdminServiceSoapBindingStub"
is known issue
Go to metalink, article: Unable To Connect To OVD 11g Webinterface Using ODSM. [ID 1282757.1]
You need to apply that patch.
I hope this helps,
Thiago Leoncio.

Dump Error in MAterial Consumption Report

Hi all Gurus
[1] I need help from your side i am doing one material consumption report in that i did all thing but it is giving me dump error while i was using sort in to ALV
so please any one help me out this .......
[2] I am Printing sum of quantity in Header area of smartform it is printing with using comma e.x 43,000 but in body area it is showing with decimal point
e.x 43.000
Following is my ALV reports code please check it it is giving me short dump while using sort ..............
I am very much in neeed
Thanx for your suggestion in advanc.....
and god bless you............
*& Report ZCONSUM
REPORT ZCONSUM.
*& Report ZCONSUMPTION
TYPE-POOLS : SLIS.
TABLES:marc,
       mara,
       makt,
       mard,
       mbew,
       mseg,
       mkpf.
TYPES:
        BEGIN OF s_mseg,
            mblnr LIKE mseg-mblnr,
            mjahr LIKE mseg-mjahr,
            zeile LIKE mseg-zeile,
            bwart LIKE mseg-bwart,
            matnr LIKE mseg-matnr,
            werks LIKE mseg-werks,
            menge LIKE mseg-menge,
            budat LIKE mkpf-budat,
            mtart LIKE mara-matnr,
            matkl LIKE mara-matkl,
        END OF s_mseg,
        BEGIN OF s_t001w,
            werks LIKE t001w-werks,
            name1 LIKE t001w-name1,
        END OF s_t001w,
        BEGIN OF s_mara,
            matnr LIKE mara-matnr,
            mtart LIKE mara-mtart,
            matkl LIKE mara-matkl,
        END OF s_mara,
        BEGIN OF s_makt,
            matnr LIKE makt-matnr,
            spras LIKE makt-spras,
            maktx LIKE makt-maktx,
        END OF s_makt,
       BEGIN OF s_calc,
            matnr       LIKE mara-matnr,
            mtart       LIKE mara-mtart,
            matkl       LIKE mara-matkl,
            maktx       LIKE makt-maktx,
           menge_t     LIKE mseg-menge,
           menge_t1    LIKE mseg-menge,
            menge_con_261   LIKE mseg-menge,
            menge_con_262   LIKE mseg-menge,
            menge_con1_261 LIKE mseg-menge,
            menge_con1_262 LIKE mseg-menge,
            menge_ret_291   LIKE mseg-menge,
            menge_ret1_291 LIKE mseg-menge,
            menge_ret_292   LIKE mseg-menge,
            menge_ret1_292 LIKE mseg-menge,
            menge_unit_301 LIKE mseg-menge,
            menge_unit1_301 LIKE mseg-menge,
            menge_unit_302 LIKE mseg-menge,
            menge_unit1_302 LIKE mseg-menge,
            menge_sub   LIKE mseg-menge,
            menge_sub1   LIKE mseg-menge,
            menge_oth   LIKE mseg-menge,
            menge_oth1 LIKE mseg-menge,
        END OF s_calc,
        BEGIN OF s_data,
            matnr       LIKE mara-matnr,
            matkl       LIKE mara-matkl,
            mtart       LIKE mara-mtart,
            maktx       LIKE makt-maktx,
            menge_t     LIKE mseg-menge,
            menge_t1    LIKE mseg-menge,
            menge_con   LIKE mseg-menge,
            menge_con1 LIKE mseg-menge,
            menge_ret   LIKE mseg-menge,
            menge_ret1 LIKE mseg-menge,
            menge_unit LIKE mseg-menge,
            menge_unit1 LIKE mseg-menge,
            menge_sub   LIKE mseg-menge,
            menge_sub1   LIKE mseg-menge,
            menge_oth   LIKE mseg-menge,
            menge_oth1 LIKE mseg-menge,
        END OF s_data.
DATA:   w_mseg TYPE s_mseg,
        i_mseg TYPE s_mseg OCCURS 0,
        w_t001w TYPE s_t001w,
        i_t001w TYPE s_t001w OCCURS 0,
        w_mara TYPE s_mara,
        i_mara TYPE s_mara OCCURS 0,
        w_makt TYPE s_makt,
        i_makt TYPE s_makt OCCURS 0,
        w_calc TYPE s_calc,
        i_calc TYPE s_calc OCCURS 0,
        w_data TYPE s_data,
        i_data TYPE s_data OCCURS 0.
DATA:   line_cnt TYPE i,
        v_temp TYPE p DECIMALS 2.
ALV DATA DECLERATION
DATA : IT_FIELD TYPE SLIS_T_FIELDCAT_ALV,
       WA_FIELD TYPE SLIS_FIELDCAT_ALV.
DATA : IT_LAYOUT TYPE SLIS_LAYOUT_ALV.
IT_LAYOUT-ZEBRA = 'X'.
IT_LAYOUT-TOTALS_TEXT = 'Grand Total'.
IT_LAYOUT-SUBTOTALS_TEXT = 'Sub Total'.
IT_LAYOUT-INFO_FIELDNAME = 'LINE_COLOR'.
DATA: WA_COMMENTRY TYPE SLIS_LISTHEADER.
DATA: IT_COMMENTRY TYPE SLIS_T_LISTHEADER.
DATA: WA_COMMENTRY1 TYPE SLIS_LISTHEADER.
DATA: IT_COMMENTRY1 TYPE SLIS_T_LISTHEADER.
DATA: WA_EVENT TYPE SLIS_ALV_EVENT.
DATA: IT_EVENT TYPE SLIS_T_EVENT.
WA_EVENT-NAME = 'TOP_OF_PAGE'.
WA_EVENT-FORM = 'TOP'.
APPEND WA_EVENT TO IT_EVENT.
DATA : WA_SORT TYPE slis_sortinfo_alv,
       IT_SORT TYPE SLIS_T_SORTINFO_ALV.
CLEAR WA_SORT.
WA_SORT-SPOS = '1'.
WA_SORT-FIELDNAME = 'MATKL'.
WA_SORT-TABNAME = 'I_DATA'.
WA_SORT-SUBTOT = 'X'.
APPEND WA_SORT TO IT_SORT.
CLEAR WA_SORT.
WA_SORT-SPOS = '2'.
WA_SORT-FIELDNAME = 'MTART'.
WA_SORT-TABNAME = 'I_DATA'.
WA_SORT-SUBTOT = 'X'.
APPEND WA_SORT TO IT_SORT.
DEFINE MAC1.
WA_FIELD-TABNAME = 'I_DATA'.
WA_FIELD-FIELDNAME = &1.
WA_FIELD-COL_POS = &2.
WA_FIELD-SELTEXT_L =&3.
WA_FIELD-DO_SUM = &4.
APPEND WA_FIELD TO IT_FIELD.
END-OF-DEFINITION.
MAC1 'MATKL'        '1' 'MATERIAL GROUP' 'X'.
MAC1 'MTART'        '2' 'MATERIAL TYPE' 'X'.
MAC1 'MATNR'        '3' 'MATERIAL NO' 'X'.
MAC1 'MAKTX'        '4' 'DESCRIPTION' 'X'.
MAC1 'MENGE_CON1'   '5' 'CONSUMPTION FOR PERIOD' 'X'.
MAC1 'MENGE_CON'    '6' 'CONSUMPTION FOR CUMULATIVE' 'X'.
MAC1 'MENGE_RET1'   '7' 'RETURN FROM DEPT. FOR PERIOD' 'X'.
MAC1 'MENGE_RET'    '8' 'RETURN FROM DEPT.CUMULATIVE' 'X'.
MAC1 'MENGE_UNIT1' '9' 'INTER UNIT FOR PERIOD' 'X'.
MAC1 'MENGE_UNIT'   '10' 'INTER UNIT CUMULATIVE' 'X'.
MAC1 'MENGE_SUB1'   '11' 'SUB CONTRACTOR FOR PERIOD' 'X'.
MAC1 'MENGE_SUB'    '12' 'SUB CONTRACTOR CUMULATIVE' 'X'.
MAC1 'MENGE_OTH1'   '13' 'OTHERS FOR PERIOD' 'X'.
MAC1 'MENGE_OTH'    '14' 'OTHERS CUMULATIVE' 'X'.
MAC1 'MENGE_t1'     '15' 'TOTAL FOR PERIOD' 'X'.
MAC1 'MENGE_t'      '16' 'TOTAL CUMULATIVE' 'X'.
SELECTION-SCREEN: BEGIN OF BLOCK B1 WITH FRAME TITLE text-001.
PARAMETERS: p_werks LIKE t001w-werks DEFAULT '1023' OBLIGATORY.
select-options: s_matkl     FOR mara-matkl,
                  s_mtart     FOR mara-mtart,
                  s_matnr     FOR mara-matnr,
                  s_budat     FOR mkpf-budat OBLIGATORY.
PARAMETERS: year(4) DEFAULT '2007'.
SELECTION-SCREEN:END OF BLOCK B1.
START-OF-SELECTION.
SELECT lk~mblnr
         lk~mjahr
         lk~budat
         lp~zeile
         lp~bwart
         lp~matnr
         lp~werks
         lp~menge
         ma~mtart
         ma~matkl
         INTO CORRESPONDING FIELDs OF TABLE i_mseg
         FROM MSEG AS lp INNER JOIN MKPF AS lk
         ON lkmblnr EQ lpmblnr
         AND lkmjahr EQ lkmjahr
         INNER JOIN mara AS ma
         ON mamatnr EQ lpmatnr
         WHERE lp~werks EQ p_werks
           AND lp~matnr IN s_matnr
           AND lk~budat LE s_budat-high.
      clear line_cnt.                         "Count line of i_table i_mseg
      DESCRIBE TABLE i_mseg LINES line_cnt.
      IF line_cnt GT 0.                      "If i_mseg has records
          SELECT matnr                        "Collect material description
                 maktx
                 spras
                 INTO CORRESPONDING FIELDS OF TABLE i_makt
                 FROM makt
                 FOR ALL ENTRIES IN i_mseg
                 WHERE matnr EQ i_mseg-matnr
                   AND spras EQ 'E'.
            CLEAR line_cnt.
            DESCRIBE TABLE i_makt LINES line_cnt.
            IF line_cnt GT 0.
               SORT i_makt BY MATNR ASCENDING.
               DELETE ADJACENT DUPLICATES FROM i_makt COMPARING matnr.
            ENDIF.
          SELECT werks                        "Collect plant name
                 name1
                 INTO CORRESPONDING FIELDS OF TABLE i_t001w
                 FROM t001w
                 FOR ALL ENTRIES IN i_mseg
                 WHERE werks EQ i_mseg-werks.
            CLEAR line_cnt.
            DESCRIBE TABLE i_t001w LINES line_cnt.
            IF line_cnt GT 0.
               SORT i_t001w BY werks ASCENDING.
               DELETE ADJACENT DUPLICATES FROM i_t001w COMPARING werks.
            ENDIF.
           LOOP AT i_mseg INTO w_mseg.        "Move recored into data i_tab
            w_calc-matnr = w_mseg-matnr.
            w_calc-mtart = w_mseg-mtart.
            w_calc-matkl = w_mseg-matkl.
            READ TABLE i_makt WITH KEY matnr = w_mseg-matnr INTO w_makt.
             IF sy-subrc = 0.
                w_calc-maktx = w_makt-maktx.
             ENDIF.
            IF w_mseg-bwart EQ '261' .
               w_calc-menge_con_261   = w_mseg-menge.
               IF w_mseg-budat GE s_budat-low.
                  w_calc-menge_con1_261   = w_mseg-menge.
               ENDIF.
            ENDIF.
            IF w_mseg-bwart EQ '262' .
               w_calc-menge_con_262   = w_mseg-menge.
               IF w_mseg-budat GE s_budat-low.
                  w_calc-menge_con1_262   = w_mseg-menge.
               ENDIF.
            ENDIF.
            IF w_mseg-bwart EQ '291' OR w_mseg-bwart EQ '201'.
               w_calc-menge_ret_291 = w_mseg-menge.
               IF w_mseg-budat GE s_budat-low.
                  w_calc-menge_ret1_291   = w_mseg-menge.
               ENDIF.
            ENDIF.
            IF w_mseg-bwart EQ '292' OR w_mseg-bwart EQ '202'.
               w_calc-menge_ret_292   = w_mseg-menge.
               IF w_mseg-budat GE s_budat-low.
                  w_calc-menge_ret1_292   = w_mseg-menge.
               ENDIF.
            ENDIF.
            IF w_mseg-bwart EQ '301'.
               w_calc-menge_unit_301   = w_mseg-menge.
               IF w_mseg-budat GE s_budat-low.
                  w_calc-menge_unit1_301   = w_mseg-menge.
               ENDIF.
            ENDIF.
            IF w_mseg-bwart EQ '302'.
               w_calc-menge_unit_302   = w_mseg-menge.
               IF w_mseg-budat GE s_budat-low.
                  w_calc-menge_unit1_302   = w_mseg-menge.
               ENDIF.
            ENDIF.
            IF w_mseg-bwart EQ '543'.
               w_calc-menge_sub   = w_mseg-menge.
               IF w_mseg-budat GE s_budat-low.
                  w_calc-menge_sub1   = w_mseg-menge.
               ENDIF.
            ENDIF.
                COLLECT w_calc INTO i_calc.
           ENDLOOP.                           "ENDLOOP of Move recored into data i_tab
          LOOP AT i_calc INTO w_calc.
            w_data-matnr   = w_calc-matnr.
            w_data-mtart   = w_calc-mtart.
            w_data-matkl   = w_calc-matkl.
            w_data-maktx   = w_calc-maktx.
            v_temp = w_calc-menge_con_261 - w_calc-menge_con_262.
            w_data-menge_con    = v_temp.
            CLEAR v_temp.
            v_temp = w_calc-menge_con1_261 - w_calc-menge_con1_262.
            w_data-menge_con1   = v_temp.
            CLEAR v_temp.
            v_temp = w_calc-menge_ret_291 - w_calc-menge_ret_292.
            w_data-menge_ret    = v_temp.
            CLEAR v_temp.
            v_temp = w_calc-menge_ret1_291 - w_calc-menge_ret1_292.
            w_data-menge_ret1    = v_temp.
            CLEAR v_temp.
            v_temp = w_calc-menge_unit_301 - w_calc-menge_unit_302.
            w_data-menge_unit    = v_temp.
            CLEAR v_temp.
            v_temp = w_calc-menge_unit1_301 - w_calc-menge_unit1_302.
            w_data-menge_unit1   = v_temp.
            CLEAR v_temp.
            w_data-menge_sub    = w_calc-menge_sub.
            w_data-menge_sub1   = w_calc-menge_sub.
            v_temp = w_data-menge_con + w_data-menge_ret + w_data-menge_unit + w_data-menge_sub.
            w_data-menge_t      = v_temp.
            CLEAR v_temp.
            v_temp = w_data-menge_con1 + w_data-menge_ret1 + w_data-menge_unit1 + w_data-menge_sub1.
            w_data-menge_t1      = v_temp.
            CLEAR v_temp.
            APPEND w_data TO i_data.
          ENDLOOP.
      ENDIF.                                  "ENDIf i_mseg has records
Display_ALV
END-OF-SELECTION.
DATA : DATE(85),
         DATE_LOW(10),
         DATE_HIGH(10),
         MSK TYPE STRING,
         DATE1(10),
         date2(10).
WA_COMMENTRY-TYP = 'H'.
WA_COMMENTRY-INFO = 'Material Consumption Report'.
APPEND WA_COMMENTRY TO IT_COMMENTRY.
CLEAR WA_COMMENTRY.
CONCATENATE S_BUDAT-LOW6(2) '/' S_BUDAT-LOW4(2) '/' S_BUDAT-LOW+0(4) INTO DATE1.
CONCATENATE S_BUDAT-high6(2) '/' S_BUDAT-high4(2) '/' S_BUDAT-high+0(4) INTO DATE2.
CONCATENATE 'Material Consumption Report :' DATE1 'To' date2 INTO DATE SEPARATED BY SPACE.
WA_COMMENTRY-TYP = 'S'.
WA_COMMENTRY-INFO = DATE.
APPEND WA_COMMENTRY TO IT_COMMENTRY.
CLEAR WA_COMMENTRY.
*SORT I_DATA BY   MTART MATKL .
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
   I_CALLBACK_PROGRAM                = SY-REPID
   I_CALLBACK_TOP_OF_PAGE            = 'TOP_OF_PAGE'
   I_BACKGROUND_ID                   = 'ALV_BACKGROUNG'
I_GRID_TITLE                      = 'STOCK LEDGER SUMMARY'
   IS_LAYOUT                         = IT_LAYOUT
   IT_FIELDCAT                       = IT_FIELD
IT_SORT                           = IT_SORT
I_SAVE                            = 'X'
   IT_EVENTS                         = IT_EVENT
TABLES
    T_OUTTAB                          = I_DATA.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
FORM TOP .
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
    IT_LIST_COMMENTARY       = IT_COMMENTRY
I_LOGO                   = 'INOXLOGO'
I_END_OF_LIST_GRID       =
I_ALV_FORM.
REFRESH IT_COMMENTRY.
ENDFORM.                    " TOP-OF-PAGE

It is giving me error on sort statement
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_CALLBACK_PROGRAM = SY-REPID
I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
I_BACKGROUND_ID = 'ALV_BACKGROUNG'
I_GRID_TITLE = 'STOCK LEDGER SUMMARY'
IS_LAYOUT = IT_LAYOUT
IT_FIELDCAT = IT_FIELD
IT_SORT = IT_SORT <<<<<<<<<<<<<<<<<<<<<<<<<<<
I_SAVE = 'X'
IT_EVENTS = IT_EVENT
TABLES
T_OUTTAB = I_DATA.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

Dump Error while using SSFCOMP_PDF_PREVIEW FM

Hi All,
   While calling the Fm SSFCOMP_PDF_PREVIEW in the purchase order print program ZSAPFM06P (copy of the standard programe) im getting a dump error
Runtime Errors POSTING_ILLEGAL_STATEMENT
Date and Time 11.01.2012 17:31:01
function ssfcomp_pdf_preview.
data: l_dummy type standard table of tline.
clear: pdf_data, pdf_size.
convert otf to pdf
call function 'CONVERT_OTF'
       exporting
            format                = 'PDF'
       importing
            bin_filesize          = pdf_size
            bin_file              = pdf_data
       tables
            otf                   = i_otf[]
            lines                 = l_dummy
       exceptions
            err_max_linewidth     = 1
            err_format            = 2
            err_conv_not_possible = 3
            others                = 4.
if sy-subrc <> 0.
    raise convert_otf_to_pdf_error.
endif.
>>>>>> call screen 0300 starting at 1 1.
Endfunction.
Can any one help me.
Thanks in Advance.

Hi,
Thanks for your reply.
I have created my own smartform for purchase order print & i have copied standard PO Print program and in that i am calling my Z samrtform.
Our Client wants that printpreview and PDF conversion through ME22N. So i have used SSFCOMP_PDF_PREVIEW to full fill my requirement.
Is there any other way to show both preview and able to convert to PDF and storing in local PC if user wants.
Pls help.
Thanks,
Vishnu

Short dump error report

What is the purpose of short dump error report generated by the system? What r the major parts/section of this report?

hi please look through this:
Whenever any transaction or any process is executed it hits an ABAP code.
If there is any issue in executing the code the situation is called "ABAP DUMP" or 'Short Dump'
Transaction ST22 is used to check any ABAP Dump within a given duration.
U can also fix the issue with the help of ABAP editor (Transaction Code SE38) if u r good with ABAP.
you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
sap-basis sap-basisAll Groups Ignore this text box. It is used to detect spammers.If you enter anything into this text box, no search results will be displayed.
SAP Groups > Technical-functional > sap-basis > Message
About This Group | Invite peers to join this group
<< Prev thread < Prev msg Next msg > Next thread >>
short dump----urgent
Reply from Keith Lewis on 5/2/2003 3:22:00 AM
Good explanation Joy, but it is not only limited to the current day and
yesterday. If you click on the Selection button you can select previous
days as well. In fact you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
Cheers
Keith
SAP R/3 Support Specialist
Information Services International
Tel +44 1664 41 6178 Mobile +44 7887 627818
E-mail email@removed
Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp
Dear sreenivas
If you receive an error message in the R/3 System log (SM21), or if you
see
a terminated update in the update service analysis transaction (SM13), or
DB
realated error ,check for dumps using the dump analysis transaction
(transaction ST22), or choose Tools -> Administration -> Monitoring ->
Dump
analysis.
Transaction ST22 enables you to analyze short dumps from the current and
previous day.
The dump analysis function shows you:
What happened
What you can do
How to correct the error
The dump analysis function also provides an error ID and keywords that you
can use to search in SAPNet, as well as information about:
The system environment
Users and transactions
Transaction ST22 enables you to analyze the following data:
Date, time, user, client
Contents of system and data fields
Contents of internal tables and application tables
ST22 is a very nice feature in SAP. This is where all the system errors
and users mistakes showed up. If there is a problem that you cannot
solve and you contact SAP support, they look at this area to analyze it.
This gives us lead where to handle the problems.
Error analysis
How to correct the error
System environment
User, transaction...
Information on where termination occurred
Contents of system fields
Chosen variables
Active calls / events
Internal notes
Active calls in SAP kernel
List of ABAP programs affected
List of internal tables
Directory of application tables (contents)
Directory of data areas (administration information)
Directory of data areas (contents)
ABAP control blocks CONT
End of runtime analysis
i think this would be helpful
regards
sravani

Short Dump Error

Hi Everyone,
I'm loading 690k odd records to cube
I am facing short dump error while data request is processed to cube.
In ST22 i'm getting Timeout Error.
Buffer time is set for 10mins to process
Can anyone guide me in this issue.
Thanks in advance

Hi,
Due to data volume your load took more than 7hrs. in general time out time is 7hrs. so in your case its may exceeded.
Try to increase time out time for your info package.
Go to your info pack--> menu scheduler --> time out time--> increase 7 hrs to 14hrs and trigger your load again. if its full load delete failed load and retrigger.
Thanks

Short dump error when using count(*)

Hi Experts
I am getting a short dump error when selecting the records >= current date - 30 see the coding and comment please correct the coding I want to know the ztable records it is important for command interface.
I have 1402345 records available after deleting the records but as the memory is not enough it is giving short dump error
select count(*) from ZINT_TABLE
select count(*) from ZINT_MSGS
   select * from zint_data
             nto table izint_d2 . "PACKAGE SIZE 20000
   where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
endselect.**
report z_eslp_command_records.
data: cnt type i.
data: cnt2 type i.
data: cnt3 type i.
data: cnt4 type i.
DATA:
     w_date1 like sy-datum .
DATA:
     w_date2 like sy-datum.
data: izint_msgs type table of zint_msgs.
data: izint_data type table of zint_data.
data: izint_m2 type table of zint_msgs.
data: izint_d2 type table of zint_data.
INITIALIZATION.
w_date1 = sy-datum - 30.
w_date2 = sy-datum - 30.
select * from zint_data
             into table izint_data PACKAGE SIZE 3000
             where STATUS = 'OK' AND CREATED_ON <= w_date1.   " ZERO
endselect.
select * from zint_msgs
             into table izint_msgs PACKAGE SIZE 3000
              where CREATED_ON <= w_date2.              " ZERO
endselect.
select * from zint_data
             into table izint_d2 PACKAGE SIZE 20000
   where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
endselect.
select * from zint_msgs
             into table izint_m2 PACKAGE SIZE 20000
where CREATED_ON >= w_date2.                            " VALUE
endselect.
select * from zint_data
            into table izint_data2
where STATUS = 'OK' AND CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
select * from zint_msgs
            into table izint_msgs2
where CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
sort izint_data by created_on ascending.
sort izint_msgs by created_on ascending.
sort izint_d2 by created_on ascending.
sort izint_m2 by created_on ascending.
describe table izint_data lines cnt.
describe table izint_msgs lines cnt2.
describe table izint_d2 lines cnt3.
describe table izint_m2 lines cnt4.
write:/ ' Note: THE RECORDS COUNTED SHOULD SHOW ZERO ELSE THE SCRIPT FAILED TO RUN' color 3.
skip.
write:/ '1. Records counted in ZINT_DATA   <=current date - 30                   :' color 2,                        cnt color 4.
write:/ '2. Records available in ZINT_DATA >=current date - 30                   'color 4,                   cnt3 color 4 .
skip.
write:/ '2. Records counted in ZINT_MSGS   <=current date - 30                   :' color 2                 ,                      cnt2 color 4.
write:/ '4. Records available in ZINT_MSGS >=current date - 30                   'color 4 ,            cnt4 color 4 .
TOP-OF-PAGE.
WRITE:/55(60) ' WAGNERS INVESTMENT LIMITED '.
WRITE:/50(40) ' Command Interface Data' CENTERED .
WRITE:/50(40) '----
' CENTERED .
FORMAT INTENSIFIED ON.
SKIP.
"FORMAT COLOR COL_HEADING.
ULINE.
FORMAT COLOR 1.
END-OF-PAGE.

Answer

Getting a program Dump Error in Herarchial ALV

Hello All,
I am getting a dump error when I am executing the below program. Kindly help as I am not getting the output. However all the subroutines are getting properly populated with data. Getting a dump error while calling the function : REUSE_ALV_HIERSEQ_LIST_DISPLAY
Pasted below are both the question and solution. Copy the solution in SE38 and execute it to check out the dump error.
Kindly help.
Thanks,
Vinod.
QUESTION :-
Objective
     Hierarchical ALV for displaying Sales documents per customer
Design
     Create a program that will allow the user to display all customers that have placed Sales Orders in the given date range. The user will have an ability to drill-down to see the sales order items per customer.
     Selection screen fields
          Sales order creation date (range)
          Customer number (range)
     Output
          Header
               Customer Number
               Customer Name
               Total Order value (sum of order values from items below)
          Details
Sales order number
Material number
Order quantity
Order value
Reference
     Tables: KNA1, VBAK, VBAP
     Transaction VA03 (Sales order)
SOLUTION :-
*& Report Z_HALV_32722                                                *
REPORT Z_HALV_32722                            .
TYPE-POOLS: slis.
TABLES : kna1,
         vbak.
SELECT-OPTIONS: s_cst_no FOR kna1-kunnr.
SELECT-OPTIONS: s_cr_dt FOR vbak-erdat.
DATA : BEGIN of ty_hdr,
        kunnr TYPE vbak-kunnr,
        name1 TYPE kna1-name1,
        netwr TYPE vbak-netwr,
        END of ty_hdr,
        gt_hdr LIKE TABLE OF ty_hdr,
        gs_hdr LIKE LINE OF gt_hdr.
DATA : BEGIN of ty_ln,
        kunnr TYPE vbak-kunnr,
        vbeln TYPE vbap-vbeln,
        matnr TYPE vbap-matnr,
        kwmeng TYPE vbap-kwmeng,
        netwr TYPE vbap-netwr,
        END of ty_ln,
        gt_ln LIKE TABLE OF ty_ln,
        gs_ln LIKE LINE OF gt_ln.
DATA : BEGIN of ty_hdr1,
        kunnr TYPE vbak-kunnr,
        END of ty_hdr1,
        gt_hdr1 LIKE TABLE OF ty_hdr1,
        gs_hdr1 LIKE LINE OF gt_hdr1.
DATA : gt_fc TYPE slis_t_fieldcat_alv,
       gs_fc LIKE LINE OF gt_fc,
       gs_k_fld TYPE slis_keyinfo_alv,
       gt_layout TYPE slis_layout_alv,
       gv_repid TYPE sy-repid.
START-OF-SELECTION.
gv_repid = sy-repid.
perform fetch_data.
perform prepare_fc.
perform prepare_layout.
perform show_output.
*&      Form fetch_data
      text
--> p1        text
<-- p2        text
form fetch_data .
SELECT kunnr
INTO CORRESPONDING FIELDS OF TABLE gt_hdr1
FROM vbak
WHERE vbak~kunnr IN s_cst_no
AND vbak~erdat IN s_cr_dt.
DELETE ADJACENT DUPLICATES FROM gt_hdr1 COMPARING kunnr.
LOOP AT gt_hdr1 INTO gs_hdr1.
SELECT SINGLE vbakkunnr kna1name1 SUM( vbak~netwr )
INTO (gs_hdr-kunnr, gs_hdr-name1, gs_hdr-netwr)
FROM vbak INNER JOIN kna1
ON vbakkunnr = kna1kunnr
WHERE vbak~kunnr = gs_hdr1-kunnr
GROUP BY vbakkunnr kna1name1.
APPEND gs_hdr TO gt_hdr.
SELECT vbakkunnr vbapvbeln vbapmatnr vbapkwmeng vbap~netwr
INTO CORRESPONDING FIELDS OF TABLE gt_ln
FROM vbap INNER JOIN vbak
ON vbapvbeln = vbakvbeln
WHERE vbak~kunnr = gs_hdr1-kunnr.
ENDLOOP.
endform.                    " fetch_data
*&      Form prepare_fc
      text
--> p1        text
<-- p2        text
form prepare_fc .
CLEAR gs_k_fld.
gs_k_fld-header01 = 'KUNNR'.
gs_k_fld-item01   = 'KUNNR'.
CLEAR gs_fc.
gs_fc-fieldname = 'KUNNR'.
gs_fc-tabname   = 'GT_HDR'.
gs_fc-seltext_l = text-001.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'NAME1'.
gs_fc-tabname   = 'GT_HDR'.
gs_fc-seltext_l = text-002.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'NETWR'.
gs_fc-tabname   = 'GT_HDR'.
gs_fc-seltext_l = text-003.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'VBELN'.
gs_fc-tabname   = 'GT_LN'.
gs_fc-seltext_l = text-004.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'MATNR'.
gs_fc-tabname   = 'GT_LN'.
gs_fc-seltext_l = text-005.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'KWMENG'.
gs_fc-tabname   = 'GT_LN'.
gs_fc-seltext_l = text-006.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'NETWR'.
gs_fc-tabname   = 'GT_LN'.
gs_fc-seltext_l = text-007.
APPEND gs_fc TO gt_fc.
endform.                    " prepare_fc
*&      Form prepare_layout
      text
--> p1        text
<-- p2        text
form prepare_layout .
gt_layout-colwidth_optimize = 'X'.
gt_layout-expand_fieldname = 'TST'.
endform.                    " prepare_layout
*&      Form show_output
      text
--> p1        text
<-- p2        text
form show_output .
CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
EXPORTING
I_INTERFACE_CHECK              = ' '
    I_CALLBACK_PROGRAM             = gv_repid
I_CALLBACK_PF_STATUS_SET       = ' '
I_CALLBACK_USER_COMMAND        = ' '
    IS_LAYOUT                      = gt_layout
    IT_FIELDCAT                    = gt_fc
IT_EXCLUDING                   =
IT_SPECIAL_GROUPS              =
IT_SORT                        =
IT_FILTER                      =
IS_SEL_HIDE                    =
I_SCREEN_START_COLUMN          = 0
I_SCREEN_START_LINE            = 0
I_SCREEN_END_COLUMN            = 0
I_SCREEN_END_LINE              = 0
I_DEFAULT                      = 'X'
I_SAVE                         = ' '
IS_VARIANT                     =
IT_EVENTS                      =
IT_EVENT_EXIT                  =
    i_tabname_header               = 'GT_HDR'
    i_tabname_item                 = 'GT_LN'
I_STRUCTURE_NAME_HEADER        =
I_STRUCTURE_NAME_ITEM          =
    is_keyinfo                     = gs_k_fld
IS_PRINT                       =
IS_REPREP_ID                   =
I_BYPASSING_BUFFER             =
I_BUFFER_ACTIVE                =
IMPORTING
E_EXIT_CAUSED_BY_CALLER        =
ES_EXIT_CAUSED_BY_USER         =
tables
    t_outtab_header                = GT_HDR[]
    t_outtab_item                  = GT_LN[]
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.
endform.                    " show_output

Everything looks fine with the gt_layout, it is not an internal table, so no need to append to it, it is simply a structure, but you do tell it that TST is the expand field, but there is no field of this name in your internal for the header, so add it like this.
DATA : BEGIN of ty_hdr,
kunnr TYPE vbak-kunnr,
name1 TYPE kna1-name1,
netwr TYPE vbak-netwr,
<b>TST type c,</b>
END of ty_hdr,
Doing so should make you program work correctly.
Regards,
Rich Heilman
Message was edited by:
        Rich Heilman

Dump error when clicked on text elements in SAP Script window

Hi All,
There is an inclusion in SAP Script. I have written the code in driver program. I need to pass the value to SAP Script in the requested position. But when I go to SE71 > Form Name > Change or Display > MAIN Window > Text Elements > I get a dump error.
Category               ABAP Programming Error
Runtime Errors         DATA_LENGTH_TOO_LARGE
Except.                CX_SY_RANGE_OUT_OF_BOUNDS
ABAP Program           SAPLSTXK
Application Component BC-SRV-SCR
Date and Time          30.04.2014 20:00:08
Short text
     Invalid partial field access: Length is too large
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLSTXK" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
      caught in
     procedure "TOKEN_COMMENT" "(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:
    In the executed program "SAPLSTXK", the system attempted to access the field
    "ITF_TOKEN" of the type "C" and with the length 255 using the length 272.
    However, a partial field access with a length specification that is
    larger than the field length is not allowed.
How to correct the error
    Reduce the length used to access the field.
    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:
    "DATA_LENGTH_TOO_LARGE" "CX_SY_RANGE_OUT_OF_BOUNDS"
    "SAPLSTXK" or "LSTXKFRN"
    "TOKEN_COMMENT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
2937 * todo empty comment ???
2938       if g_tm_open    eq true or     " Section
2939          g_tm_b_close eq true.
2940         l_token = '\chcbpat0'.
2941         l_len = strlen( l_token ).
2942         token_control = true.
2943         assign l_token to <itf1>.
2944         perform put_itf1_new using l_len.
2945         perform token_line_begin changing l_next_token.
2946       else.                          " without section
2947         concatenate '\chcbpat0\line' g_cf_string l_cbpat_token into l_token.
2948         l_len = strlen( l_token ).
2949         token_control = true.
2950         assign l_token to <itf1>.
2951         perform put_itf1_new using l_len.
2952       endif.
2953     elseif l_next_token-code eq ')L'.         " \par
2954       l_token = '\par'.
2955       l_len = strlen( l_token ).
2956       token_control = true.
2957       assign l_token to <itf1>.
2958       perform put_itf1_new using l_len.
2959     elseif l_next_token-code eq '(C' or       " \par + format
2960            l_next_token-code eq ')C' or
2961            l_next_token-code eq '(&' or
2962            l_next_token-code eq 'TA' or
2963            l_next_token-code eq 'SC' or
2964            l_next_token-code eq 'ST'.
2965       concatenate '\chcbpat0\par' g_pf_string g_cf_string l_cbpat_token into l_token.
2966       l_len = strlen( l_token ).
>>>>>       itf_token(l_len) = l_token.
2968       token_control = true.
2969       assign l_token to <itf1>.
2970       perform put_itf1_new using l_len.
2971     endif.
2972
2973 * Step 7: (L to disarm
2974   if g_compose eq true and
2975      l_next_token-code eq '(L'.
2976     perform read_next_itf_token(rstxscan) using p_token.
2977   endif.
2978
2979 ENDFORM.                    " token_comment
2980 *&---------------------------------------------------------------------*
2981 *&      Form create_lang_info
2982 *&---------------------------------------------------------------------*
2983 *       add default language to rtf
2984 *----------------------------------------------------------------------*
2985 *      -->P_HEADER text
2986 *      <--P_RESULT text
How do I open the text elements? I need to pass the variable inside SAP Script.
Please Help. The requirement is pending from very long. Not able to rectify this issue.
Regards,
Rekha

Hi,
There is a SAP Note about this problem
566794 - Runtime error: STRING_OFFSET_TOO_LARGE during conversion
Correction Instructions
Correction Instructions
Software Component
Valid from
Valid to
Number
SAP_BASIS
46B
46D
473267
SAP_BASIS
610
620
473185
Support Packages & Patches
Support Packages
Software Component
Release
Support Package
SAP_BASIS
46B
SAPKB46B48
46C
SAPKB46C39
46D
SAPKB46D28
610
SAPKB61027
620
SAPKB62014
Regards
Miguel

Dump error while creating Invoicing document

Moderator note - this is the same problem as identified in thread Error is generated in Print workbench function ISU_INV_BILL_PREPARE. Thread locked and poster notified of rules violation.
Hi Experts,
I am new to ISU application.Please provide solution for below mentioned dump error.
The error is generated in Print workbench function ISU_INV_BILL_PREPARE which is called from application form IS_U_BILL (/1PWB/SAPL20020100218092657) when I'm trying to generate invoice for the bill in EASIBI.
Error analysis
Short text of error message:
Unexpected ELSE case: field sy-subrc with value 0 (/1PWB/200201002180926
57 )
Long text of error message:
Something has occurred in a CASE or IF construct which the
developer did not expect, or which is not permissible here.
System Response
Procedure
Note the field name and field value from the message as well as the
data pattern which lead to the error. Create a problem message.
Technical information about the message:
Message class....... "E9"
Number.............. 898
Variable 1.......... "sy-subrc"
Variable 2.......... 0
Variable 3.......... "/1PWB/20020100218092657"
| Variable 4.......... " "
Thanks in Advance.
Vaseem
Edited by: William Eastman on Mar 9, 2010 2:34 PM
Edited by: William Eastman on Mar 9, 2010 2:36 PM

Hi Experts,
Please reply..... It's very important.
Thanks
Vaseem
Moderator note: DO NOT beg for answers, or suggest that you need an immediate reply. Read the rules of engagement here Research Resources and Rules of Engagement
Edited by: William Eastman on Mar 9, 2010 2:24 PM

Error in smartform when printing multiple pages

Hi,
I m using a smartform which have two pages in it,
i m able to save and activate it without any error message and when i run the function module generated to chk my smartform
it runs fine and diplays two pages i m using.
but as i m attaching this form with my driver program it is giving an error message while running . the error message is " No other output defined in main window."
Please help me out to resolve the issue.

Re: error in smartform when printing multiple pages
dharani tadikonda
Thanks for this answer. It is absolutely correct.

I am getting dump error while running one report in one select query

Hi,
While running a report program, I am getting a dump error in one select query. So could you please correct the select query so that I can't face the dump error.
SELECT vbeln parvw kunnr INTO CORRESPONDING FIELDS OF TABLE l_t_vbpa
FROM vbpa
FOR ALL ENTRIES IN l_t_backorder_item
WHERE vbeln = l_t_backorder_item-vbeln AND
( ( parvw = c_we AND kunnr IN rng_shipto ) OR ( parvw = c_ag AND
kunnr IN rng_soldto ) ) .
<removed by moderator>
Best Regards,
BDP
Edited by: Thomas Zloch on Apr 30, 2010 12:31 PM

Hi Bansidhar,
It would be helpful if you could tell what type of dump it is.
If it is a timeout you should check whether l_t_backorder_item is empty - in this case ALL document numbers are selected. f you get the timeout with a populated table consider converting the l_t_backorder_item table into one ore more ranges tables - the select with ranges tables is way quicker than 'for all entries'. But take care the ranges table has not to many entries - the SAP SQL converter puts this into one huge SQL statement and this might become too big to be handled by the database (depends on the actual underlying database).
I would also consider splitting the SELECT into two (2nd one with 'appending into table') to make the code easier to understand It also helps the database system determining a strategy for the select.
Regards,
Gerd Rother

Dump error while creating or double click the info package

Hello experts,
I have actived infocube 0FIAR_C03 in BI content. Ago, The creation infopackage have been deleted in the past , today, I created a infopackage, while I update mode selected u2018initialize delta processu2019, then click save button , the system prompt u2018Deltas already loaded for request REQU_D64R47LDUSZHY9CBIB86WMLFJ init.selection; no 2. initu2019, I canoti save it for my setting. Why is this?
Then I have search cause in SDN, and I have reference OSS Note 852443 to do .
Note 852443 have mention some table: RSSELDONE、RSSDLINIT、RSSDLINITSEL、ROOSPRMSC、ROOSPRMSF.
I have to delete that request of record using se16 in these tables: RSSELDONE、RSSDLINIT、RSSDLINITSEL.
in my BI 7.0 system, ROOSPRMSC、ROOSPRMSF is no any data.
I was no found delta queue in RSA7.
Now . Dump error while creating or double click the info package, how can I change this?
Please let me know the solution.
Thanks for your help.
Best Regards
Steve

Here are some links which deals with same issue.
Re: Dump In Infopackage
Re: Getting into Short dump at the time of selecting InfoPackage to execute for
Short dump while performing init in infopackage
Re: Infopackage going into short dump
Thanks.

Dump error in smartforms

Similar Messages

Maybe you are looking for