Regarding runtime error

Hi Gurus,
I am facing error while creating sales order.I am working on excise( TAXINN).while creating standard sales order there is no runtime error.But when i change customer pricing procedure relevant to tax it shows runtime error.there is no such error in TAXINJ.
ii have given following link for details.
http://www.4shared.com/file/63968817/42eae8b2/Runtime_error.html
please guide me.
Regards
Hemant

i was wrong in confiruration.

Similar Messages

Regarding runtime error DBIF_RSQL_SQL_ERROR and exception CX_SY_OPEN_SQL_DB

Hi All,
I am loading a COPA cube from a DSO.
There are about 15million records to be loaded. every time i try loading the data, 1 or 2 Data packages gets stuck and finally it leads to a runtime error DBIF_RSQL_SQL_ERROR with exception CX_SY_OPEN_SQL_DB.
When i checked in SM21 transaction code, i got the following message
10:41:52 BTC 018 500 AMRUKV                     BY O Deadlock occurred
10:41:53 BTC 018 500 AMRUKV                     BY 4 Database error 60 at INS access to table /BIC/FCSDV
10:41:53 BTC 018 500 AMRUKV                     BY 0 > ORA-00060: deadlock detected while waiting for resource
10:41:54 BTC 018 500 AMRUKV                     AB 0 Run-time error "DBIF_RSQL_SQL_ERROR" occurred
10:41:58 BTC 018 500 AMRUKV                     AB 1 > Short dump "080818 104154 s0173bel PB100 " generated
10:41:58 BTC 018 500 AMRUKV                     D0 1 Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20080818104154s0173bel_PB1_00 AMRUKV 500 )
In transaction code ST22 i got the following message:
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          18.08.2008 10:41:54
Short text
     SQL error in the database when accessing a table.
What happened?
     The database system detected a deadlock and avoided it by rolling back
     your transaction.
What can you do?
     If possible (and necessary), repeat the last database transaction in the
      hope that locking the object will not result in another deadlock.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
      in procedure "WRITE_ICFACT" "(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:
     The database system recognized that your last operation on the database
     would have led to a deadlock.
     Therefore, your transaction was rolled back
     to avoid this.
     ORACLE always terminates any transaction that would result in deadlock.
     The other transactions involved in this potential deadlock
     are not affected by the termination.
How to correct the error
    Database error text........: "ORA-00060: deadlock detected while waiting for
     resource"
    Internal call code.........: "[RSQL/INSR//BIC/FCSDVD_C02 ]"
    Please check the entries in the system log (Transaction SM21).
    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:
    "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "GPD3UMZD6V4YAKZAIWAOCYLV07Y" or "GPD3UMZD6V4YAKZAIWAOCYLV07Y"
    "WRITE_ICFACT"
    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
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "WRITE_ICFACT" "(FORM)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
Can anybody suggest on what can be done?
Thanks in Advance,
Regards
A.T

Hi ,
This is a table space issue....
u will be getting a Dump...as DBIF_RSQL_SQL_ERROR check in ST22. in this DUMP if u scroll down u will find the table for which this is failing. Actually this is like some of the table related to the DSO is not having sufficient space to cary out the transaction. hence it is failing.
U can also see in DB02--> Deadlock....u will see that there is a deadlock for this table. So find the table from ST22 and ask ur basis team to increase the space for this table....
This can be solved only by increasing the space of the table...no other solution....ask help from ur basis team.
Thanks
Sandeep

Urgent: Regarding Runtime Error in FM

hi,
i had made a Function Module which will reterive the production order,but when i use it in the program it gives runtime error.Plzz help me how to solve this problem.
1st i am pasting the code which i had written:-
FUNCTION ZFIND_PRDORD.
""Local Interface:
*" IMPORTING
*"     VALUE(QP_CHARG) LIKE CHVW-CHARG OPTIONAL
*"     VALUE(P_AUFNR) LIKE CHVW-AUFNR OPTIONAL
*" EXPORTING
*"     VALUE(P_RETVAL) LIKE CHVW-AUFNR
DATA : BEGIN OF T_CHVW OCCURS 0,
              XZUGA LIKE CHVW-XZUGA,
              WERKS LIKE CHVW-WERKS,
              MATNR LIKE CHVW-MATNR,
              CHARG LIKE CHVW-CHARG,
              AUFNR LIKE CHVW-AUFNR,
              EBELN LIKE CHVW-EBELN,
              MBLNR LIKE CHVW-MBLNR,
              ZEILE LIKE CHVW-ZEILE,
              BUDAT LIKE CHVW-BUDAT,
              SHKZG LIKE CHVW-SHKZG,
              BWART LIKE CHVW-BWART,
              MENGE LIKE CHVW-MENGE,
              MEINS LIKE CHVW-MEINS,
              KZBEW LIKE CHVW-KZBEW,
          END OF T_CHVW.
SELECT XZUGA WERKS MATNR CHARG AUFNR EBELN
MBLNR ZEILE BUDAT SHKZG BWART MENGE MEINS KZBEW
FROM CHVW INTO TABLE T_CHVW
WHERE CHARG EQ QP_CHARG
and XZUGA = ' '
AND BWART = '101'
and aufnr eq p_aufnr
AND KZBEW = 'F' .
P_RETVAL = T_CHVW-AUFNR.
ENDFUNCTION.
Now i am displaying the program for testing this FM which gives the runtime error:-
TABLES : CHVW.
SELECT-OPTIONS : P_CHARG FOR CHVW-CHARG,
                 P_AUFNR FOR CHVW-AUFNR .
CALL FUNCTION 'ZFIND_PRDORD'
EXPORTING
   QP_CHARG       = P_CHARG
   P_AUFNR        = P_AUFNR
IMPORTING
   P_RETVAL      = P_AUFNR.
WRITE : / 'SDSQDA' .
Plzz help me out as how to solve this problem as i have to use it in
the main program.
regards,
ric.s

HI SANTOSH,
I had changed according what u said and it is not giving runtime error .
but it is not giving the value as if i send the value of batch and the prd orderr. plz tell me how do it get the output.
i had written the code of program like this:-
TABLES : CHVW.
Parameters : P_CHARG like CHVW-CHARG,
             P_AUFNR like CHVW-AUFNR.
DATA: PRD LIKE CHVW-AUFNR.
CALL FUNCTION 'ZFIND_PRDORD'
EXPORTING
QP_CHARG = P_CHARG
P_AUFNR = P_AUFNR
IMPORTING
P_RETVAL = PRD.
WRITE : / PRD .
PLZ HELPMEOUT HOW TO DO THIS.

Regarding Runtime error in ALV List Display.

am using following to display data in ALV List.
but after executing of program am getting runtime error called 'Field Symbol has Not been assigned' .
please tell me how to correct the error.
Very urgent
Suitable answers rewarded with Maximum Ponits...
REPORT zmatrix.
TYPE-POOLS: slis.
TABLES: agr_define, sza5_d0700.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-006.
SELECT-OPTIONS: s_role FOR agr_define-agr_name OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b1.
                       D A T A                                       *
TYPES: BEGIN OF ty_agr_1251_inf,
       agr_name TYPE agr_1251-agr_name,
       object   TYPE agr_1251-object,
       field    TYPE agr_1251-field,
       low(20) TYPE c,
       high     TYPE agr_1251-high,
       infty    TYPE t582s-infty,
       itext    TYPE t582s-itext,
       END OF ty_agr_1251_inf.
TYPES: BEGIN OF ty_agr_1251_tcode,
       agr_name TYPE agr_1251-agr_name,
       object   TYPE agr_1251-object,
       field    TYPE agr_1251-field,
       low(20) TYPE c,
       high     TYPE agr_1251-high,
       tcode    TYPE tstct-tcode,
       ttext    TYPE tstct-ttext,
       END OF ty_agr_1251_tcode.
TYPES: BEGIN OF ty_t582s,
       infty TYPE agval,
       itext TYPE t582s-itext,
       END OF ty_t582s.
TYPES: BEGIN OF ty_code,
       tcode TYPE tstct-tcode,
       ttext TYPE ttext_stct,
END OF ty_code.
TYPES: BEGIN OF ty_inf,
       infty TYPE t582s-infty,
       itext TYPE t582s-itext,
       END OF ty_inf.
TYPES: BEGIN OF ty_role,
       agr_name TYPE agr_1251-agr_name,
       END OF ty_role.
TYPES: BEGIN OF tys_role_dtls,
         agr_name TYPE agr_name,
         value     TYPE c,
         property TYPE c,
       END OF tys_role_dtls.
TYPES: BEGIN OF tys_infotype_final,
       text(60),
       text1(60),
       value(4),
       END OF tys_infotype_final.
                    I N T E R N A L   T A B L E S                    *
DATA: wa_infotyp_final TYPE tys_infotype_final.
DATA: t_infotyp_final TYPE TABLE OF tys_infotype_final.
DATA: BEGIN OF wa_infotyp_dtls,
         infty     TYPE infty,
         itext     TYPE intxt,
         role_dtls TYPE TABLE OF tys_role_dtls,
      END OF wa_infotyp_dtls.
DATA: BEGIN OF wa_tcode_dtls,
         tcode     TYPE tcode,
         ttext     TYPE ttext_stct,
         role_dtls TYPE TABLE OF tys_role_dtls,
       END OF wa_tcode_dtls.
DATA: t_infotyp_dtls      LIKE   TABLE OF wa_infotyp_dtls,
      t_tcode_dtls        LIKE   TABLE OF wa_tcode_dtls,
      t_role_dtls         TYPE   TABLE OF tys_role_dtls,
      wa_role_dtls        TYPE   tys_role_dtls.
DATA: wa_inf              TYPE   ty_inf,
      t_inf               TYPE   STANDARD TABLE OF ty_inf.
DATA: wa_role             TYPE   ty_role,
      t_role              TYPE   STANDARD TABLE OF ty_role.
DATA: wa_tcode            TYPE   ty_code,
      t_tcode             TYPE   TABLE OF ty_code.
DATA: wa_agr_1251_inf     TYPE   ty_agr_1251_inf.
DATA: wa_agr_1251_tcode   TYPE   ty_agr_1251_tcode.
DATA: t_agr_1251_inf      TYPE STANDARD TABLE OF ty_agr_1251_inf.
DATA: t_agr_1251_tc       TYPE STANDARD TABLE OF ty_agr_1251_tcode.
DATA: wa_582s             TYPE   ty_t582s.
DATA: t_582s              TYPE STANDARD TABLE OF ty_t582s.
DATA: t_range_tcode       TYPE RANGE OF tcode.
DATA: t_range_inf         TYPE RANGE OF infotyp.
DATA: wa_range_inf        LIKE LINE OF t_range_inf.
DATA: wa_range_tcode      LIKE LINE OF t_range_tcode.
DATA: wa_field TYPE slis_fieldcat_alv.
DATA: t_field TYPE slis_t_fieldcat_alv.
                  VARIABLES FOR OLE                                  *
DATA: text(20),
      count(20).
DATA: text1(30).
DATA: agr_name       TYPE   agr_1251-agr_name.
DATA: flag           TYPE   i VALUE '0'.
DATA: string1        TYPE   string.
DATA: str            TYPE   string VALUE 'SAP%'.
DATA: count1         TYPE   i VALUE '0'.
*&   Event START-OF-SELECTION
START-OF-SELECTION.
PERFORM f100_get_inf_data.
PERFORM f200_process_inf_data.
count1 = 1.
PERFORM f300_prepare_field_catalog.
PERFORM f110_main_data.
PERFORM f400_display_data.
PERFORM f100_get_trans_data.
*&      Form f110_main_data
      text
FORM f110_main_data.
wa_infotyp_final-text = 'Access to Infotypes'.
APPEND wa_infotyp_final TO t_infotyp_final.
wa_infotyp_final-text = 'Infotype'.
wa_infotyp_final-text1 = 'Description'.
APPEND wa_infotyp_final TO t_infotyp_final.
wa_infotyp_final-text = '*'.
wa_infotyp_final-text1 = 'Acess to all Infotypes'.
LOOP AT t_role INTO wa_role WHERE agr_name <> ' '.
   READ TABLE t_agr_1251_inf INTO wa_agr_1251_inf
   WITH KEY agr_name = wa_role-agr_name field = 'INFTY' low = '*'.
   IF syst-subrc = 0.
     wa_infotyp_final-value = 'X'.
   ENDIF.
ENDLOOP.
APPEND wa_infotyp_final TO t_infotyp_final.
LOOP AT t_inf INTO wa_inf WHERE infty <> ' '.
    wa_infotyp_final-text = wa_inf-infty.
    wa_infotyp_final-text1 = wa_inf-itext.
    LOOP AT t_role INTO wa_role WHERE agr_name <> ' '.
   Role Name
      CLEAR wa_role_dtls.
      flag = 1.
      wa_role_dtls-agr_name = wa_role-agr_name.
    For Value D & F
      READ TABLE t_agr_1251_inf INTO wa_agr_1251_inf
      WITH KEY agr_name = wa_role-agr_name field = 'AUTHC'..
      IF syst-subrc EQ 0.
        IF wa_agr_1251_inf-low = 'R'.
          wa_infotyp_final-value = 'D'.
        ELSE.
          wa_infotyp_final-value = 'F'.
        ENDIF.
      ENDIF.
      APPEND wa_role_dtls TO t_role_dtls.
      APPEND wa_infotyp_final TO t_infotyp_final.
    ENDLOOP.
ENDLOOP.
ENDFORM.                    "f110_main_data
*&      Form f100_get_inf_data
      text
FORM f100_get_inf_data.
                      Logic for Infotypes                            *
SELECT aagr_name aobject
         afield alow a~high
         INTO TABLE t_agr_1251_inf
         FROM agr_1251 AS a INNER JOIN agr_define AS b
         ON aagr_name EQ bagr_name
WHERE ( ( aobject EQ 'P_ORGIN' OR aobject EQ 'P_PERNR' )
AND   ( aagr_name IN s_role ) AND ( bagr_name NOT LIKE str ) ).
ENDFORM.                    "f100_get_inf_data
*&      Form f200_get_inf_process_data
      text
FORM f200_process_inf_data.
LOOP AT t_agr_1251_inf INTO wa_agr_1251_inf.
    IF wa_agr_1251_inf-high IS INITIAL.
      CLEAR wa_range_inf.
      wa_range_inf-sign = 'I'.
      wa_range_inf-option = 'EQ'.
      wa_range_inf-low = wa_agr_1251_inf-low.
      APPEND wa_range_inf TO t_range_inf.
    ELSE.
      CLEAR wa_range_inf.
      wa_range_inf-sign = 'I'.
      wa_range_inf-option = 'BT'.
      wa_range_inf-low = wa_agr_1251_inf-low.
      wa_range_inf-high = wa_agr_1251_inf-high.
      APPEND wa_range_inf TO t_range_inf.
    ENDIF.
ENDLOOP.
SORT t_range_inf.
DELETE ADJACENT DUPLICATES FROM t_range_inf.
IF t_range_inf IS NOT INITIAL.
    SELECT infty itext FROM t582s
    INTO TABLE t_582s
    WHERE sprsl = 'EN' AND infty IN t_range_inf.
    IF syst-subrc EQ 0.
    ENDIF.
ENDIF.
LOOP AT t_agr_1251_inf INTO wa_agr_1251_inf.
    IF wa_agr_1251_inf-high IS INITIAL.
      READ TABLE t_582s INTO wa_582s
        WITH KEY infty = wa_agr_1251_inf-low.
      IF syst-subrc EQ 0.
        wa_agr_1251_inf-infty = wa_582s-infty.
        wa_agr_1251_inf-itext = wa_582s-itext.
        MODIFY t_agr_1251_inf FROM wa_agr_1251_inf
                     TRANSPORTING infty itext.
        IF syst-subrc EQ 0.
        ENDIF.
      ENDIF.
    ELSE.
      CLEAR count.
      LOOP AT t_582s INTO wa_582s
              WHERE infty GE wa_agr_1251_inf-low
                AND infty LE wa_agr_1251_inf-high.
        IF count LE 1.
          wa_agr_1251_inf-high = space.
          wa_agr_1251_inf-infty = wa_582s-infty.
          wa_agr_1251_inf-itext = wa_582s-itext.
          MODIFY t_agr_1251_inf FROM wa_agr_1251_inf
                       TRANSPORTING infty itext.
          IF syst-subrc EQ 0.
            CLEAR wa_582s.
          ENDIF.
        ELSE.
          wa_agr_1251_inf-high = space.
          wa_agr_1251_inf-infty = wa_582s-infty.
          wa_agr_1251_inf-itext = wa_582s-itext.
          APPEND wa_agr_1251_inf TO t_agr_1251_inf.
        ENDIF.
        CLEAR wa_agr_1251_inf.
        count = count + 1.
      ENDLOOP.
    ENDIF.
ENDLOOP.
wa_role-agr_name = ' '.
APPEND wa_role TO t_role.
wa_role-agr_name = ' '.
APPEND wa_role TO t_role.
LOOP AT t_agr_1251_inf INTO wa_agr_1251_inf.
    IF wa_agr_1251_inf IS NOT INITIAL.
      wa_role-agr_name = wa_agr_1251_inf-agr_name.
      wa_inf-infty = wa_agr_1251_inf-infty.
      wa_inf-itext = wa_agr_1251_inf-itext.
      APPEND wa_role TO t_role.
      APPEND wa_inf TO t_inf.
    ENDIF.
ENDLOOP.
SORT t_role BY agr_name.
DELETE ADJACENT DUPLICATES FROM t_role.
SORT t_inf BY infty.
DELETE ADJACENT DUPLICATES FROM t_inf.
ENDFORM.                    "f200_get_process_inf_data
*&      Form f100_get_trans_data
      text
FORM f100_get_trans_data.
              Logic for Transaction Codes                            *
SELECT aagr_name aobject
           afield alow a~high
    INTO CORRESPONDING FIELDS OF TABLE t_agr_1251_tc
    FROM agr_1251 AS a
    INNER JOIN agr_define AS b ON aagr_name EQ bagr_name
    WHERE a~agr_name IN s_role
      AND a~object EQ 'S_TCODE'.
ENDFORM.                    "f100_get_trans_data
*&      Form f200_process_trans_data
      text
FORM f200_process_trans_data.
LOOP AT t_agr_1251_tc INTO wa_agr_1251_tcode.
    IF wa_agr_1251_tcode-high IS INITIAL.
      CLEAR wa_range_tcode.
      wa_range_tcode-sign = 'I'.
      wa_range_tcode-option = 'EQ'.
      wa_range_tcode-low = wa_agr_1251_tcode-low.
      APPEND wa_range_tcode TO t_range_tcode.
    ELSE.
      CLEAR wa_range_tcode.
      wa_range_tcode-sign = 'I'.
      wa_range_tcode-option = 'BT'.
      wa_range_tcode-low = wa_agr_1251_tcode-low.
      wa_range_tcode-high = wa_agr_1251_tcode-high.
      APPEND wa_range_tcode TO t_range_tcode.
    ENDIF.
ENDLOOP.
SORT t_range_tcode.
DELETE ADJACENT DUPLICATES FROM t_range_tcode.
IF t_range_tcode IS NOT INITIAL.
    SELECT tcode
           ttext
      FROM tstct
      INTO TABLE t_tcode
      WHERE sprsl EQ 'E'
        AND tcode IN t_range_tcode.
    IF sy-subrc EQ 0.
    ENDIF.
ENDIF.
SORT t_agr_1251_tc BY agr_name.
LOOP AT t_agr_1251_tc INTO wa_agr_1251_tcode.
    IF wa_agr_1251_tcode-high IS INITIAL.
      READ TABLE t_tcode INTO wa_tcode
        WITH KEY tcode = wa_agr_1251_tcode-low.
      IF syst-subrc EQ 0.
        wa_agr_1251_tcode-tcode = wa_tcode-tcode.
        wa_agr_1251_tcode-ttext = wa_tcode-ttext.
        MODIFY t_agr_1251_tc FROM wa_agr_1251_tcode
                     TRANSPORTING tcode ttext.
        IF syst-subrc EQ 0.
        ENDIF.
      ENDIF.
    ELSE.
      CLEAR count.
      LOOP AT t_tcode INTO wa_tcode
              WHERE tcode GE wa_agr_1251_tcode-low
                AND tcode LE wa_agr_1251_tcode-high.
        IF count LE 1.
          agr_name = wa_agr_1251_tcode-agr_name.
          wa_agr_1251_tcode-high = space.
          wa_agr_1251_tcode-tcode = wa_tcode-tcode.
          wa_agr_1251_tcode-ttext = wa_tcode-ttext.
          MODIFY t_agr_1251_tc FROM wa_agr_1251_tcode
                       TRANSPORTING tcode ttext high.
          IF syst-subrc EQ 0.
            CLEAR wa_tcode.
          ENDIF.
          count = 1.
        ELSE.
          wa_agr_1251_tcode-high = space.
          wa_agr_1251_tcode-agr_name = agr_name.
          wa_agr_1251_tcode-low = wa_tcode-tcode.
          wa_agr_1251_tcode-tcode = wa_tcode-tcode.
          wa_agr_1251_tcode-ttext = wa_tcode-ttext.
          APPEND wa_agr_1251_tcode TO t_agr_1251_tc.
        ENDIF.
        CLEAR wa_agr_1251_tcode.
        count = count + 1.
      ENDLOOP.
    ENDIF.
ENDLOOP.
LOOP AT t_agr_1251_tc INTO wa_agr_1251_tcode.
    wa_role-agr_name = wa_agr_1251_tcode-agr_name.
    APPEND wa_role TO t_role.
ENDLOOP.
SORT t_role BY agr_name.
DELETE ADJACENT DUPLICATES FROM t_role.
SORT t_tcode BY tcode.
DELETE ADJACENT DUPLICATES FROM t_tcode.
ENDFORM.                    "f200_process_trans_data
*&      Form f100_prepare_field_catalog
      text
FORM f300_prepare_field_catalog.
LOOP AT t_role INTO wa_role.
    wa_field-col_pos = count1.
    wa_field-fieldname = wa_role-agr_name.
    APPEND wa_field TO t_field.
    count1 = count1 + 1.
ENDLOOP.
ENDFORM.                    "f100_prepare_field_catalog
*&      Form f100_display_data
      text
FORM f400_display_data.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
            EXPORTING
            I_INTERFACE_CHECK              = ' '
            I_BYPASSING_BUFFER             =
            I_BUFFER_ACTIVE                = ' '
              i_callback_program             = sy-cprog
            I_CALLBACK_PF_STATUS_SET       = ' '
            I_CALLBACK_USER_COMMAND        = ' '
            I_STRUCTURE_NAME               =
            IS_LAYOUT                      =
              it_fieldcat                    = t_field[]
            IT_EXCLUDING                   =
            IT_SPECIAL_GROUPS              =
            IT_SORT                        =
            IT_FILTER                      =
            IS_SEL_HIDE                    =
            I_DEFAULT                      = 'X'
            I_SAVE                         = ' '
            IS_VARIANT                     =
            IT_EVENTS                      =
            IT_EVENT_EXIT                  =
            IS_PRINT                       =
            IS_REPREP_ID                   =
            I_SCREEN_START_COLUMN          = 0
            I_SCREEN_START_LINE            = 0
            I_SCREEN_END_COLUMN            = 0
            I_SCREEN_END_LINE              = 0
            IR_SALV_LIST_ADAPTER           =
            IT_EXCEPT_QINFO                =
            I_SUPPRESS_EMPTY_DATA          = ABAP_FALSE
          IMPORTING
            E_EXIT_CAUSED_BY_CALLER        =
            ES_EXIT_CAUSED_BY_USER         =
              TABLES
                t_outtab                       = t_infotyp_final[]
             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.                    "f100_display_data

this are the wasy u can build a field catalog...
1.----
FORM fill_fieldcat .
DATA: fld(30),
idx(2) TYPE n.
DEFINE no_output.
fieldcatalog-fieldname = &1.
fieldcatalog-no_out = 'X'.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
END-OF-DEFINITION.
DEFINE catalog.
fieldcatalog-fieldname = &1.
fieldcatalog-seltext_s = &2.
if not &3 is initial.
fieldcatalog-seltext_m = &3.
else.
fieldcatalog-seltext_m = fieldcatalog-seltext_s.
endif.
if not &4 is initial.
fieldcatalog-seltext_l = &4.
else.
fieldcatalog-seltext_l = fieldcatalog-seltext_m.
endif.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
END-OF-DEFINITION.
catalog 'AVAIL_BASE'
'Base Qty.'
'Base Qty. Available'
'Base Quantity Available'.
catalog 'AVAIL_SALES'
'Sales Qty.'
'Sales Qty. Available'
'Sales Quantity Available'.
LOOP AT t_char_data.
idx = sy-tabix.
CONCATENATE 'CHR' idx INTO fld.
catalog fld
t_char_data-atbez
t_char_data-atbez
t_char_data-atbez.
ENDLOOP.
ADD 1 TO idx.
WHILE idx LE 15.
CONCATENATE 'CHR' idx INTO fld.
no_output fld.
ADD 1 TO idx.
ENDWHILE..
fieldcatalog-fieldname = 'EXACT'.
fieldcatalog-checkbox = 'X'.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
2.----
FORM fieldcatalog.
REFRESH fc. CLEAR fc.
fc-tabname = 'HEADER'.
fc-fieldname = 'KUNNR'.
fc-ref_tabname = 'MSKU'.
APPEND fc. CLEAR fc.
fc-tabname = 'HEADER'.
fc-fieldname = 'NAME1_K'.
fc-ref_tabname = 'KNA1'.
fc-ref_fieldname = 'NAME1'.
APPEND fc. CLEAR fc.
fc-tabname = 'HEADER'.
fc-fieldname = 'TOTAL'.
fc-ref_tabname = 'MBEW'.
fc-ref_fieldname = 'SALK3'.
APPEND fc. CLEAR fc.
fc-tabname = 'LIST'.
fc-fieldname = 'MATNR'.
fc-ref_tabname = 'MSKU'.
APPEND fc. CLEAR fc.
fc-tabname = 'LIST'.
fc-fieldname = 'MAKTX'.
fc-ref_tabname = 'MAKT'.
fc-no_out = 'X'.
APPEND fc. CLEAR fc.
fc-tabname = 'LIST'.
fc-fieldname = 'CHARG'.
fc-ref_tabname = 'MSKU'.
APPEND fc. CLEAR fc.
fc-tabname = 'LIST'.
fc-fieldname = 'WERKS'.
fc-ref_tabname = 'MSKU'.
fc-no_out = 'X'.
APPEND fc. CLEAR fc.
fc-tabname = 'LIST'.
fc-fieldname = 'NAME1_W'.
fc-ref_tabname = 'T001W'.
fc-ref_fieldname = 'NAME1'.
fc-no_out = 'X'.
APPEND fc. CLEAR fc.

Regarding runtime error ehile execution of Mail step in workflow

Hi all when i execute mail step in workflow i am getting following error-
SQL error in the database when accesing a table.
How to correct the error
   Database error text........: "SQL system error. MSGID= Job=038082/DEV05/WP02"
   Internal call code.........: "[RSQL/INSR/ARFCSDATA ]"
   Please check the entries in the system log (Transaction SM21).
   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:
   "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
   "SAPLARFC" or "LARFCU03"
   "END_TRANSACTION_NONE_LOCAL_UPD"
   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
   (Unconverted)".
   3. If the problem occurs in a problem of your own or a modified SAP
   program: The source code of the program
      In the editor, choose "Utilities->More
Please guide.
Thanks.

Hi Sanjay,
Firstly are you using Send mail Activity or are u calling Fm SO_DOCUMENT_SEND_API1.
Well I suppose u are calling the FM, in that case just check the data that you are fetching before calling this FM. This error is related to sql query so check your select statements used before sending mail.
Hope this helps.

Regarding Runtime error with MB_MIGO_BADI

Hi,
I have implemented badi MB_MIGO_BADI for MIGO transaction for GR. I have added 3 fields to the header level. If i save it it is saving(i Have created a Ztable to store it.).
If i give the material document number its showing the contents of the fields i have added.
But we can display the same GR through ME23N also. In ME23N transaction if i click on GR document, Its going for dump. The problem with field symbol.
Code is:
field-symbols <fs2> type MSEG.
        assign ('(SAPLMIGO)mseg') to <fs2>.
        <fs2>-zzoctno = WA_OCT_DET-OCT_NOTE.
        <fs2>-zzoctdate = WA_OCT_DET-OCT_DATE.
        <fs2>-zzmatdate = WA_OCT_DET-MAT_RECP_DATE.
its not asssiging   ('(SAPLMIGO)mseg') to <fs2> .....when coming through ME23N.
The same statement is working fine through MIGO code.
Please let me know the solution
thanks,
kishore

Hello,
Change this
field-symbols <fs2> type TABLE. "CHeck here
Regards,
Vasanth

Regarding runtime error in actions

Hi Experts
I faced problem when executing hiring action from pa40. I have not included 004 infotype in infogroup for hiring but still when excecuting after 0002 i get an error stating that 004 does not exist it is error in red. when i check in that same screen the icon change infogroup it shows the list of infotype which includes 004 after 0002 but when i check in img in my infogroup it does not exist.
can any one help me to solve the problem
Thank you

Hi,
To get rid of that error, when you click on change infogroup , select 004 and delete it.
You should be fine for that employee.
Check table T529A to see if your Personnel Action Type is linked to the correct infogroup which you have set up to trigger.
Hope this helps.

Runtime error in KEFC Transaction while uploading CSV format file

Hi Experts,
This is regarding Runtime Error while executing the KEFC transaction in R3D.
It is working successfully while uploading the file in Text format. But there is run time error while uploading in CSV format.
It showing "The transfer was terminated.However,content errors occured" .
Please provide the solution.
Thanks in advance.
Regards,
Priya.

Hi,
To upload a CSV file it is used FM:
CALL FUNCTION 'TEXT_CONVERT_CSV_TO_SAP'
EXPORTING
i_field_seperator = ';'
I_LINE_HEADER =
i_tab_raw_data = lt_file
i_filename = p_filename
TABLES
i_tab_converted_data = p_table
EXCEPTIONS
conversion_failed = 1
OTHERS = 2
Please check what separetor this fm and your file are using. It should be the same.
Regards,
Fernando

Runtime Error : CALL_DIALOG_CONTAINER_MISSING

Please Help, I am getting the following Dump:
Regards,
Runtime Errors         CALL_DIALOG_CONTAINER_MISSING
Date and Time          04.12.2008 10:29:33
Short tex
     Format error during parameter transfer: No further container available.
What happened?
Error in the SAP kernel.
The current ABAP "SAPMS380" program had to be terminated because the
ABAP processor detected an internal system error.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
     For a precise analysis of the error, you should supply
     documents with as many details as possible.
How to correct the error
     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
          (Unconverted)".
          3. If the problem occurs in a problem of your own or a modified SAP
          program: The source code of the program
             In the editor, choose "Utilities->More
          Utilities->Upload/Download->Download".
          4. Details about the conditions under which the error occurred or which
          actions and input led to 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:
          "CALL_DIALOG_CONTAINER_MISSING" " "
          "SAPMS380" or " "
          "SYSTEM-EXIT"
     System environment
          SAP-Release 700
          Application server... "DMATE"
          Network address...... "140.1.1.141"
          Operating system..... "Windows NT"
          Release.............. "5.2"
          Hardware type........ "4x AMD64 Level"
          Character length.... 16 Bits
          Pointer length....... 64 Bits
          Work process number.. 1
          Shortdump setting.... "full"
          Database server... "dmate"
          Database type..... "ADABAS D"
          Database name..... "AD0"
          Database user ID.. "SAPAD0"
          Char.set.... "C"
          SAP kernel....... 700
          created (date)... "Jun 23 2008 00:09:46"
          create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
          Database version. "SQLDBC 7.6.0.018 CL 119055 "
          Patch level. 166
          Patch text.. " "
          Database............. "MaxDB 7.6, MaxDB 7.7"
          SAP database version. 700
          Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
           NT 6.0"
          Memory consumption
          Roll.... 16192
          EM...... 456692560
          Heap.... 0
          Page.... 267976704
          MM Used. 833296
          MM Free. 3353920
     User and Transaction
          Client.............. 040
          User................ "CONSULTANT"
          Language key........ "E"
          Transaction......... "FB1S "
          Transactions ID..... "A5CCC1DDC388F1439FA4001143E563CA"
          Program............. "SAPMS380"
          Screen.............. "SAPMS380 0100"
          Screen line......... 0
     Information on where terminated
          Termination occurred in the ABAP program "SAPMS380" - in "SYSTEM-EXIT".
          The main program was "SAPMS380 ".
          In the source code you have the termination point in line 0
          of the (Include) program " ".
     Contents of system fields
     Name     Val.
     SY-SUBRC     0
     SY-INDEX     0
     SY-TABIX     0
     SY-DBCNT     0
     SY-FDPOS     0
     SY-LSIND     0
     SY-PAGNO     0
     SY-LINNO     1
     SY-COLNO     1
     SY-PFKEY
     SY-UCOMM
     SY-TITLE     ABAP Runtime Error
     SY-MSGTY
     SY-MSGID
     SY-MSGNO     000
     SY-MSGV1
     SY-MSGV2
     SY-MSGV3
     SY-MSGV4
     SY-MODNO     0
     SY-DATUM     20081204
     SY-UZEIT     102932
     SY-XPROG
     SY-XFORM
     Active Calls/Events
     No.   Ty.          Program                             Include                             Line
           Name
         1 EVENT        SAPMS380                            ???                                     0
           SYSTEM-EXIT
     Chosen variables
     Name
         Val.
     No.          1     Ty.      EVENT
     Name      SYSTEM-EXIT
     Internal notes
          The termination was triggered in function "imp_ldial_segment"
          of the SAP kernel, in line 1915 of the module
           "//bas/700_REL/src/krn/runt/abxdat.c#4".
          The internal operation just processed is " ".
          Internal mode was started at 20081204102932.
          Requested paging area: 32706.
     Active Calls in SAP Kernel
     Lines of C Stack in Kernel (Structure Differs on Each Platform)
     SAP (R) - R/3(TM) Callstack, Version 1.0
     Copyright (C) SAP AG. All rights reserved.
     Callstack without Exception:
     App       : disp+work.EXE (pid=5540)
     When      : 12/4/2008 10:29:32.703
     Threads   : 2
     Computer Name       : DMATE
     User Name           : SAPServiceAD0
     Number of Processors: 4
     Processor Type: EM64T Family 15 Model 4 Stepping 1
     Windows Version     : 5.2 Current Build: 3790
     State Dump for Thread Id 704
     FramePtr         ReturnAd         Param#1          Function Name
     0000000007ead400 0000000077d7047f 0000000000343e90 ntdll!NtWaitForSingleObject
     0000000007ead4a0 000000000173b1d1 0000000000000014 kernel32!WaitForSingleObjectEx
     0000000007ead6f0 00000000006179c5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)]
     0000000007ead720 0000000000b05d9c 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]
     0000000007ead770 0000000000b0afc0 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7093)]
     0000000007eae150 00000000009736d2 0000000001c859b0 disp+work!ab_rabax [abrabax.c (1231)]
     0000000007eae190 00000000009aee62 0000000007eaf4d0 disp+work!imp_ldial_segment [abxdat.c (1915)]
     0000000007eae1f0 0000000000a2b2a6 0000000007eae330 disp+work!ab_ReadData [abconcnv.c (1397)]
     0000000007eae230 0000000000a2b13a 0000000007eae330 disp+work!ReadSkipValue [abconne.c (7339)]
     0000000007eae270 0000000000a3500f 00000000000000ae disp+work!ReadSkipValue [abconne.c (7369)]
     0000000007eaf710 0000000000977317 0000000003698300 disp+work!ab_connread [abconne.c (4924)]
     0000000007eaf750 0000000000b68126 0000000007eb6050 disp+work!ab_ldiaimport [abxdat.c (2052)]
     0000000007eaf780 000000000064bc9c 0000000000000000 disp+work!ab_nmode [abtcod.c (939)]
     0000000007eb6020 0000000000b6633f 0000000007eb6078 disp+work!dy_cdiag [dynpabsv.c (1830)]
     0000000007eb9640 0000000000b0a0f0 0000000001d0b870 disp+work!ab_sdialog [abtcod.c (300)]
     0000000007eb9f30 0000000000b0c3c0 0000000000000001 disp+work!rabax_do [abrabax.c (5338)]
     0000000007eba910 0000000000a35c78 0000000001d0b8a0 disp+work!ab_rabax [abrabax.c (1497)]
     0000000007eba960 0000000000a36730 0000000800007fff disp+work!ab_mnew [abmarea.c (228)]
     0000000007eba9d0 00000000009726b8 000000000000096a disp+work!ab_mnnext [abmarea.c (297)]
     0000000007ebaa20 00000000009b07bb 000000000000000c disp+work!exp_ldial_segment [abxdat.c (1391)]
     0000000007ebaa70 0000000000a26d88 000007fe7257a190 disp+work!ab_WriteData [abconcnv.c (1590)]
     0000000007ebaaf0 0000000000a33d8b 000007fe8c76c7d8 disp+work!export_itab [abconne.c (3877)]
     0000000007ebbc60 000000000097620d 0000000000000000 disp+work!ab_connwrite [abconne.c (1992)]
     0000000007ebbca0 0000000000b69431 000007ffe7be1f88 disp+work!ab_locex [abxdat.c (1008)]
     0000000007ebbd30 0000000000b69e17 000007ffe7be1f88 disp+work!dial_local [abtcod.c (213)]
     0000000007ebbea0 0000000000ad3390 0000000000000000 disp+work!ab_cdialog [abtcod.c (203)]
     0000000007ebc740 0000000000ad50b3 0000000000000129 disp+work!ab_retdynp [abdynpro.c (671)]
     0000000007ebc7d0 0000000000679328 0000000000000129 disp+work!ab_dstep [abdynpro.c (492)]
     0000000007ebc950 000000000067d76d 000007fe725e08ae disp+work!dynpmcal [dymainstp.c (2396)]
     0000000007ebc9f0 000000000067ca2a 0000000000000000 disp+work!dynppai0 [dymainstp.c (1106)]
     0000000007ebcaa0 00000000006395c5 0000000000000000 disp+work!dynprctl [dymainstp.c (360)]
     0000000007ebfc30 00000000004dbc4c 0000000000000002 disp+work!dynpen00 [dymain.c (1646)]
     0000000007ebfeb0 000000000042f096 0000000007f62ff0 disp+work!TskhLoop [thxxhead.c (4538)]
     0000000007ebfee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1136)]
     0000000007ebff10 00000000019e84b1 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]
     0000000007ebff70 0000000077d5966c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]
     0000000007ebffa0 0000000000000000 00000000019e8340 kernel32!BaseProcessStart
     State Dump for Thread Id 11a0
     FramePtr         ReturnAd         Param#1          Function Name
     000000000c9dfe40 0000000077d5f651 0000000007f1cc60 ntdll!NtFsControlFile
     000000000c9dfeb0 00000000018ce23f 0000000000000000 kernel32!ConnectNamedPipe
     000000000c9dff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]
     000000000c9dff70 0000000077d6b69a 0000000077d6b660 msvcrt!endthreadex
     000000000c9dffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart
     List of ABAP programs affected
     Index     Typ     Program     Group     Date     Time     Size     Lang.
          0     Prg     SAPMS380          0     09.03.2008     19:40:55        182272     E
          1     Typ     SYST          0     09.09.2004     14:18:12         34816
     Directory of Application Tables
     Name                                     Date       Time       Lngth
         Val.
     Program      SAPMS380
     SYST            . .            : :          00004612
          \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0

Hello Juan,
I also received the same error while deleting the Product categories Under Responsibility of a Purchase group in Transaction PPOMA_BBP in SRM.
Once it allows me to delete them but I do the same twice I do get like below
"Runtime error MEMORY_NO_MORE_PAGING has occurred"
If you have any idea on the above issues then please help me to fix this issues.
Thanks & regards
Pratap J

Windows 7 Visual C++ runtime error

Error Message: This applicationhas requested the runtime to terminate it in an unusua lway. please contact the application support team for more info.

Hi,
To add, could you please post the whole error messages here? On which application did you receive this error message？
A runtime error is a software or hardware problem that prevents a program from working correctly. This can occur if you are running two software programs that aren't compatible, if your computer has memory problems, or if
the computer has been infected with malicious software.
For more information regarding runtime errors, please take a look at the below link:
What is a runtime error?
Also if this is related with IE, then please take a check here:
Fix Runtime Errors in Internet Explorer
Best regards
Michael Shao
TechNet Community Support

RunTime Error while saving a Sales Order

Hi All,
When i am saving a Sales Order, the system is throwing a Runtime Error.
The ABAP Code in the Runtime Error screen as follows.
          select * from (t681-kotab) appending table <cond_tab>
                 up to 1 rows
                 where kappl = se_kappl
                 and   kschl = se_kschl
                 and   datbi >= se_date
                 and   datab <= se_date
                 and   (coding_tab).
Till these days, there was no such error while saving a Sales Order.
How to resolve this issue?
Regards
Pavan

Hi,
The below piece of code is trying to get the contents of the table mentioned in T681-KOTAB.
select * from (t681-kotab) appending table <cond_tab>
up to 1 rows
where kappl = se_kappl
and kschl = se_kschl
and datbi >= se_date
and datab <= se_date
and (coding_tab).
The reason could be is someone has screwed up the entries in T681 table. Check that out.
Try to put a break point on this SELECT query and see what the value of T681-KOTAB holds before the SELECT query. Check whether such a table entry exists in DB.
Let me know if you are still stuck up.
If you can send me the ST22 dump of the run time error, i might be able to help you more on this.
Hope this helps.
Thanks,
Balaji

WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR

hi to all experts,
whenever i try to delete a particular sale order im getting a runtime error
stating that
Short text
    Screen: Illegal message
What happened?
    The current screen processing action was terminated since a situat
    occurred where the application could not continue.
    This is probably due to an error in the ABAP program or in the cur
    screen.
Error analysis
    The program attempted to issue a " " message during "Exit Command" processing.
    This is an illegal operation.
    The program was terminated.
    Screen name.............. "SAPMV45A"
    Screen number............ 4001
Trigger Location of Runtime Error
    Program                                 SAPMV45A
    Include                                 MV45AFZZ
    Row                                     370
    Module type                             (FORM)
    Module Name                             USEREXIT_SAVE_DOCUMENT
SourceCde
              message e001(zm) WITH text-335 ltab-kunnr text-334.
            else.
              if ktab-jkunnr <> ltab-kunnr.
                ktab-jkunnr = ltab-kunnr.
                jobsitecode = ltab-kunnr.
                CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input = jobsitecode
                  IMPORTING
                  output = jobsitecode.
                SELECT SINGLE * FROM kna1 WHERE kunnr = jobsitecode.
                IF sy-subrc = 0.
                  ktab-jname1 = kna1-name1.
                  ktab-jstras = kna1-stras.
                ENDIF.
                chg_flg = 'X'.
              endif.
            endif.
          else.
            message e001(zm) WITH text-336.
* Validation for relationship between Sold-to Party and Ship-to Party
*          if ktab-ckunnr+0(4) NE ktab-jkunnr+0(4).
*            message e001(zm) WITH text-335 ktab-jkunnr text-337 ktab-ckunnr.
*          endif.
          custcode1 = ktab-ckunnr.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
            EXPORTING
              input = custcode1
            IMPORTING
              output = custcode1.
          jobsitecode1 = ktab-jkunnr.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
            EXPORTING
              input = jobsitecode1
            IMPORTING
              output = jobsitecode1.
          SELECT SINGLE * FROM knvp
          WHERE kunnr = custcode1
            AND vkorg = vbak-vkorg
            AND vtweg = vbak-vtweg
            AND spart = vbak-spart
            AND parvw = 'WE'
Error analysis
    The program attempted to issue a " " message during "Exit Command"
    This is an illegal operation.
    The program was terminated.
    Screen name.............. "SAPMV45A"
    Screen number............ 4001
Trigger Location of Runtime Error
    Program                                 SAPMV45A
    Include                                 MV45AFZZ
    Row                                     370
    Module type                             (FORM)
    Module Name                             USEREXIT_SAVE_DOCUMENT

Hi,
Seems there is some problem with the user exit USEREXIT_SAVE_DOCUMENT..
Put a breakpoint and see.
Regards,
Nagaraj

WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR " Screen: Illegal message"

Hi Experts,
While deleting a sales order giving run time error. PFB runtime error details.
If you know any OSS message, please let m know. I tried, but there is no luck.
Short text
    Screen: Illegal message
What happened?
    The current screen processing action was terminated since a situation
    occurred where the application could not continue.
    This is probably due to an error in the ABAP program or in the current
    screen.
What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator.
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
Error analysis
    The program attempted to issue a " " message during "Exit Command" processing.
    This is an illegal operation.
    The program was terminated.
    Screen name.............. "SAPMV45A"
    Screen number............ 4001
How to correct the error
    The program must be modified to correct the error.
    The modification must be made in "Exit Command" processing.
    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
    (Unconverted)".
Source Code Extract
Line SourceCde
    1 *---------------------------------------------------------------------*
    2 *       FORM YVBEP_LESEN                                              *
    3 *---------------------------------------------------------------------*
    4 *       Lesen der Tabelle YVBEP (nicht sortiert)                      *
    5 *---------------------------------------------------------------------*
    6 FORM YVBEP_LESEN USING US_POSNR
    7                        US_ETENR
    8               CHANGING CH_TABIX.
    9
   10   YVBEP = SPACE.
   11   YVBEP-MANDT = VBAK-MANDT.
   12   YVBEP-VBELN = VBAK-VBELN.
   13   YVBEP-POSNR = US_POSNR.
   14   YVBEP-ETENR = US_ETENR.
   15   READ TABLE YVBEP.
   16   IF SY-SUBRC > 0.
   17     MESSAGE E506 WITH US_POSNR US_ETENR.
   18   ENDIF.
>>>>>   CH_TABIX = SY-TABIX.
   20
   21 ENDFORM.
Could you please help on this issue.
Thanks
Srinu

Hi Srinu,
it looks like you got the error message Schedule line &1 &2 is missing in table YVBEP while deleting the sales order.
It seems, that there are no SAP notes regarding this issue. Do you have this issue with all orders or with a single order?
If only a single order causes this issue, maybe something was wrong during an update.
If you get this error for many orders, then custom code (modification, enhancement, user exit in MV45AFZZ, ...) may be the reason for it.
If you have no custom code in module pool SAPMV45A, then contact SAP for this issue.
Regards,
Klaus

Portal runtime error while selecting page layout in WPC editor

Hello,
in web page composer, editing page, when i click on "select page layout" I have a portal runtime error popup.
The logfile shows the following :
#1.5 #005056834112005E0000000C00000FA800048E28A94966CC#1282205196819#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#1016#149##n/a##7ff9c93eab6811dfa9c70000003307de#SAPEngine_Application_Thread[impl:3]_15##0#0#Error##Java###10:06_19/08/10_0010_3344350
[EXCEPTION]
#1#com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in java compiling
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: E:
usr
sap
EPD
JC00
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
com.sap.netweaver.bc.util
lib
bc.util.public_api.jar(com/sapportals/wcm/WcmException.java):24: class WcmException is public, should be declared in a file named WcmException.java
(source unavailable)
1 error
I have the same by clicking on "check assignments"
Any help ?
Thanks

Hello Jego.
We faced the same issue after upgrade to EHP1 SP07 last week and managed to solve it by modification of layout.jsp and com.sap.nw.wpc.layoutmanager.LayoutBean within com.sap.nw.wpc.designtime.par. SAP's code requires an additional catch handler, so it is better to rise an OSS message.
As a workaround you may change a default layout for wpc main page (good for new pages) or manually edit output.xml for existing pages.
Best regards,
Aliaksandr Zhukau

Runtime Error in ALV Tree Output

Dear All, I am trying to create a ALV Tree using Class cl_gui_alv_tree. The Report Shows the Output with the first Node but when i try to expand it is dumping with a runtime error GETWA_NOT_ASSIGNED in class CL_ALV_TREE_BASE and method SET_ITEMS_FOR_COLUMN. The Reason being the data which was copied in the initial node display to mt_outtab is getting refreshed.
Can any one of you help me the reason for the table getting refreshed. Do i need to pass any data.
I am doing the following steps.
1. Create Container,
2. Create Tree Class object
3. Generate the Field Catalog.
4. Set table for first display " With empty internal table
5. Generate the Hierarchy
6. Call the Method Frontend Update.
Let me know if i had missed any steps in the process.
Thank you,
Regards,
Swaroop Patri

One reason for getting this error is using local defined tables for it_outtab parameter in the below code:
To get rid of the dump, define two distinct output tables globally: one is an empty table which you will pass to the below method, other one is your real output table whose size increases dependently.
CALL METHOD go_tree->set_table_for_first_display
      EXPORTING
        is_hierarchy_header = ls_hier_header
      CHANGING
        it_outtab           = gt_data_e "Empty table
        it_fieldcatalog     = gt_fcat_tree.

Regarding runtime error

Similar Messages

Maybe you are looking for