Regarding Transport dump error

Hi Experts,
In BI quality system,while importing one request has been failed with RC=8 due to all DB buffers of application server wwpbiqd1 were synchronized and failed with following dump:
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_RSR_X_MESSAGE
Termination occurred in the ABAP program "SAPLRRMS" - in "RRMS_X_MESSAGE".
the main program was "RSPRGGSFNAN ".
In the source code you have the termination point in line 82 of the (Include) program "LRRMSU13".
can anybody please give me some inputs.
I searched in SDN but i did not proper solution.
Thanks
Lakshmi

The error looks for me kind of basis activity required!
Did you replicated all the datasources in target system before transport ?
I would suggest recollect the objects
1 IO, Cube/DSO / IA
2 DS
3 TRFN , DTP , IP
4 PC
Release one after one after checking them in quality , assume if 1st request fails you will have to transport all of them .. to avoid it transport 1 and 2 and check if they are ok then release 3 and then ... 4

Similar Messages

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.

Regarding dump error in MMBE

hi experts good morning,
                  when i execute tc mmbe it is showing dump error sometimes back it worked fine and now it is showing dump error ,,i m giving the error below plz have a look and help me.....
ShrtText
    Syntax error in program "SAPLMBBS ".
What happened?
    Error in ABAP application program.
    The current ABAP program "RMMMBESTN" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    In program "SAPLMBBS ", the following syntax error occurred
    in the Include "LMBBSU07 " in line 75:
    "The column name "WAERS" has two meanings. ABAP/4 Open SQL statement."
    Author and last person to change the Include are:
    Author "SAP "
    Last changed by "SAP "
Error analysis
    In program "SAPLMBBS ", the following syntax error occurred:
    "The column name "WAERS" has two meanings. ABAP/4 Open SQL statement."
Trigger Location of Runtime Error
    Program                                 RMMMBESTN
    Module type                             (FORM)
    Module Name                             EKPO_LESEN

Hi,
Please find the SAP notes. There are several notes for this.
Regards,

ABAP dump Error while creating service order in PCUI.

Hi Experts,
                 We are getting following ABAP dump error while creating service order in PCUI which is working fine in GUI.
Runtime Errors         RAISE_EXCEPTION
Date and Time          02.01.2008 14:55:38
Short text
Exception condition "TYPE_NOT_FOUND" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
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
A RAISE statement in the program "CL_CRM_ELEMDESCR==============CP" raised the
exception
condition "TYPE_NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
|    function module from the display of active calls.
We have added custom fields in the service application. these custom fields with Z-structure & data elements are included in BSP structure CRMT_BSP_SRV_OIC_SRCHRES in development system.But the same Z structure & custom fields are exist in the production system but not included in BSP Structue CRMT_BSP_SRV_OIC_SRCHRES.
This may be the reason resulting this ABAP dump error in PCUI while creating Service order.
How these Z structures can be included in the BSP Structure CRMT_BSP_SRV_OIC_SRCHRES in production system?
Helpful answers would be rewrded max points as it is high priority issue.
Regards,
Basavaraj Patil

Hi Thirumala,
Thnaks for the reply.
            I have enhanced service application using transaction EEWB to add new custom fields. these fields are there in Z structure created by the system in production system. All the transports are moved to target system. Problem is that Z structure( contains custom fields) created while doing EEWB is not included in BSP structure.
I f transports are missed to move to target system, Is there any other alternative to solve this problem?
Regards,
Basavaraj Patil

Short dump error in program SAPMV50A after modification

Dear gurus
i have done some modification in vl02n through Badi and it is working fine in Development server.
when i transport it to quality server and test it
it giving a short dump in vl02n while vl01n is working perfectly fine and showing my modification too..
below is the error mentioned
Database error text........: "Unsupported database type in parameter/column
    (168)."
   Internal call code.........: "[RSQL/READ/LIKP ]"
   Please check the entries in the system log (Transaction SM21).
   If the error occures in a non-modified SAP program, you may be able t
   find an interim solution in an SAP Note.
   If you have access to SAP Notes, carry out a search with the followin
   keywords:
   "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
   "SAPMV50A" or "MV50AFDB"
   "LIKP_SELECT"
   If you cannot solve the problem yourself and want to send an error
   notification to SAP, include the following information:
Please help
Regards
Saad Nisar

i have created two append structure in standard tables of LIKP & LIPS which are activated and so as LIKP and LIPS
my Badi is also activated and my customized program is also activated.
While making outbound delivery in Quality server it works fine but when i want to make changes in that created delivery it throws dump error
short text
   SQL error in the database when accessing a table.
issing RAISING Clause in Interface
   Program                                 SAPMV50A
   Include                                 MV50AFDB
   Row                                     14
   Module type                             (FORM)
   Module Name                             LIKP_SELECT
rigger Location of Exception
   Program                                 SAPMV50A
   Include                                 MV50AFDB
   Row                                     20
   Module type                             (FORM)
   Module Name                             LIKP_SELECT

Dump Error in QA

Hi Frds
While running my program in DEV,the output is coming perfectly .
But transporting the same program to QA and running im getting Dump Error .In our QA we 1 lakhs Records.
How to solve the problem ,i given the coding below .
Pls Correct my mistake and give some tips.
TYPE-POOLS:SLIS.
TABLES : EKPO,MARC,EBAN,MSEG,MARD,MARA,MAKT,MLGN.
DATA:BODY        TYPE SLIS_T_FIELDCAT_ALV,
     HEADER      TYPE SLIS_FIELDCAT_ALV,
     GD_LAYOUT   TYPE SLIS_LAYOUT_ALV,
     GD_REPID    LIKE SY-REPID.
DATA : PO TYPE I,
       TGR TYPE I.
      CHECK TYPE I.
TGR = 0.
*CHECK = 0.
DATA : MATNR LIKE MARA-MATNR,
       WERKS LIKE MARD-WERKS,
       LGORT LIKE MARD-LGORT,
       BUKRS LIKE EKPO-BUKRS.
DATA : BEGIN OF ITAB OCCURS 0,
       MATNR LIKE MARA-MATNR,
       MEINS LIKE MARA-MEINS,
       MAKTX LIKE MAKT-MAKTX,
       MINBE LIKE MARC-MINBE,
       LGNUM LIKE MLGN-LGNUM,
       LGORT LIKE MARD-LGORT,
       EBELN LIKE EKPO-EBELN,
       EBELP LIKE EKPO-EBELP,
       MENGE LIKE EKPO-MENGE,
       MENG1 LIKE MSEG-MENGE,
       DQT   LIKE MSEG-MENGE,
       BANFN LIKE EBAN-BANFN,
       MENG2 LIKE EBAN-MENGE,
       END OF ITAB.
DATA : BEGIN OF IMAT OCCURS 0,
       MATNR LIKE MARA-MATNR,
       MEINS LIKE MARA-MEINS,
       MAKTX LIKE MAKT-MAKTX,
       MINBE LIKE MARC-MINBE,
       WERKS LIKE MARD-WERKS,
       LGORT LIKE MARD-LGORT,
       END OF IMAT.
DATA : BEGIN OF IEKPO OCCURS 0,
       EBELN LIKE EKPO-EBELN,
       EBELP LIKE EKPO-EBELP,
       MENGE LIKE EKPO-MENGE,
       BUKRS LIKE EKPO-BUKRS,
       MATNR LIKE EKPO-MATNR,
       LOEKZ LIKE EKPO-LOEKZ,
       WERKS LIKE EKPO-WERKS,
       LGORT LIKE EKPO-LGORT,
       END OF IEKPO.
DATA : BEGIN OF IMSEG OCCURS 0,
       EBELN LIKE MSEG-EBELN,
       EBELP LIKE MSEG-EBELP,
       MENGE LIKE MSEG-MENGE,
       MATNR LIKE MSEG-MATNR,
       LGNUM LIKE MSEG-LGNUM,
       BWART LIKE MSEG-BWART,
       END OF IMSEG.
DATA : BEGIN OF IMLGN OCCURS 0,
       MATNR LIKE MLGN-MATNR,
       LGNUM LIKE MLGN-LGNUM,
       END OF IMLGN.
DATA : BEGIN OF IEBAN OCCURS 0,
       BANFN LIKE EBAN-BANFN,
       STATU LIKE EBAN-STATU,
       MATNR LIKE EBAN-MATNR,
       MENGE LIKE EBAN-MENGE,
       WERKS LIKE EBAN-WERKS,
       LGORT LIKE EBAN-LGORT,
       BADAT LIKE EBAN-BADAT,
       LOEKZ LIKE EBAN-LOEKZ,
END OF IEBAN.
SELECTION-SCREEN: BEGIN OF BLOCK 01.
SELECTION-SCREEN: BEGIN OF BLOCK 02 WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS MATERIAL FOR MATNR.
SELECT-OPTIONS COMPANY FOR BUKRS .
SELECT-OPTIONS PLANT    FOR WERKS OBLIGATORY.
SELECT-OPTIONS STORAGE FOR LGORT OBLIGATORY.
SELECTION-SCREEN: END OF BLOCK 02.
SELECTION-SCREEN: END OF BLOCK 01.
AT SELECTION-SCREEN.
PERFORM MATERIAL.   "GET MATERIAL
START-OF-SELECTION.
PERFORM POS.   "GET POS
SORT IEKPO BY EBELN EBELP.
PERFORM GRS.   "GET GR QTY
PERFORM PRS.   "GET OPEN PR NUMBER
PERFORM READ.
PERFORM FIELDCATALOG.
PERFORM BUILD_LAYOUT.
GET ALV DISPLAY
PERFORM ALVDISPLAY.
*&      FORM MATERIAL
      TEXT
FORM MATERIAL.
SELECT MARAMATNR MARAMEINS
         MAKT~MAKTX
         MARC~MINBE
         MARDWERKS MARDLGORT
    INTO CORRESPONDING FIELDS OF TABLE IMAT
    FROM MARA INNER JOIN MAKT ON MAKTMATNR = MARAMATNR
              INNER JOIN MARC ON MARCMATNR = MARAMATNR
              INNER JOIN MARD ON MARDMATNR = MARAMATNR
    WHERE MARA~MATNR IN MATERIAL AND
          MARD~WERKS IN PLANT AND
          MARD~LGORT IN STORAGE.
IF SY-SUBRC <> 0.
    MESSAGE 'NO DATA FOUND FOR THE SELECTION ' TYPE 'E'.
    EXIT.
ENDIF.
ENDFORM.                    "MATERIAL
*&      FORM POS
      TEXT
FORM POS.
LOOP AT IMAT.
    SELECT EBELN EBELP MENGE BUKRS MATNR LOEKZ WERKS LGORT
      FROM ekpo APPENDING TABLE iekpo
      WHERE MATNR = IMAT-MATNR AND
            WERKS = IMAT-WERKS AND
            LGORT = IMAT-LGORT AND
            LOEKZ EQ SPACE.
ENDLOOP.
CLEAR : IMAT, IEKPO.
ENDFORM.                    "POS
*&      FORM GRS
      TEXT
FORM GRS.
LOOP AT IEKPO.
   SELECT EBELN EBELP MENGE MATNR LGNUM BWART FROM MSEG APPENDING TABLE
IMSEG WHERE EBELN = IEKPO-EBELN AND
             EBELP = IEKPO-EBELP AND
             MATNR = IEKPO-MATNR AND
           ( BWART = '101' OR BWART = '105' ).
ENDLOOP.
ENDFORM.                    "GRS
*&      FORM PRS
      TEXT
FORM PRS.
LOOP AT IMAT.
    SELECT BANFN STATU MATNR MENGE WERKS LGORT BADAT LOEKZ FROM EBAN
APPENDING TABLE IEBAN
     WHERE MATNR = IMAT-MATNR AND
           STATU EQ 'N' AND
           LOEKZ EQ SPACE AND
           WERKS IN PLANT AND
           LGORT IN STORAGE.
ENDLOOP.
ENDFORM.                    "PRS
*&      FORM READ
      TEXT
FORM READ.
LOOP AT IMAT. " MAIN LOOP
    ITAB-MATNR = IMAT-MATNR.
    ITAB-MEINS = IMAT-MEINS.
    ITAB-MAKTX = IMAT-MAKTX.
    ITAB-MINBE = IMAT-MINBE.
    ITAB-LGORT = IMAT-LGORT.
    READ TABLE IMSEG WITH KEY MATNR = IMAT-MATNR.
    ITAB-LGNUM = IMSEG-LGNUM.
PO & GR *************************
   CHECK = 0.
    LOOP AT IEKPO WHERE MATNR = IMAT-MATNR. " INNER LOOP
     CHECK = 1.
      ITAB-EBELN = IEKPO-EBELN.
      ITAB-EBELP = IEKPO-EBELP.
      ITAB-MENGE = IEKPO-MENGE.
      LOOP AT IMSEG WHERE EBELN = IEKPO-EBELN AND EBELP = IEKPO-EBELP.
        " INNER INNER LOOP.
        TGR = TGR + IMSEG-MENGE.
      ENDLOOP.
      ITAB-DQT = IEKPO-MENGE - TGR.
      IF ITAB-DQT > 0.
        APPEND : ITAB.
        CLEAR : ITAB-EBELN,ITAB-EBELP,IEKPO-MENGE,TGR,ITAB-DQT.
      ENDIF.
      CLEAR : ITAB-EBELN,ITAB-EBELP,IEKPO-MENGE,TGR,ITAB-DQT.
    ENDLOOP.
    CLEAR : ITAB-EBELN,ITAB-EBELP,IEKPO-MENGE,TGR,ITAB-DQT.
PR ********************
    LOOP AT IEBAN WHERE MATNR = IMAT-MATNR.
     CHECK = 1.
      ITAB-BANFN = IEBAN-BANFN.
      ITAB-MENG2 = IEBAN-MENGE.
      APPEND ITAB.
      CLEAR : ITAB-BANFN ,ITAB-MENG2.
    ENDLOOP.
   IF CHECK = 0.
      APPEND ITAB.
   ELSEIF check = 1.
   ENDIF.
    CLEAR : IEKPO,ITAB-EBELN,ITAB-EBELP,ITAB-MENGE,ITAB-DQT.
ENDLOOP.
CLEAR : ITAB,IEKPO,IMAT,IMLGN.
ENDFORM.                    "READ
*&      FORM BUILD_LAYOUT
      TEXT
FORM BUILD_LAYOUT.
GD_LAYOUT-NO_INPUT          = 'X'.
GD_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
ENDFORM.                    " BUILD_LAYOUT
*&      FORM FIELDCATALOG
      TEXT
FORM FIELDCATALOG .
HEADER-COL_POS = '1'.
HEADER-SELTEXT_L = 'MATERIAL CODE'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'MATNR'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '2'.
HEADER-SELTEXT_L = 'MATERIAL DESC'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'MAKTX'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '3'.
HEADER-SELTEXT_L = 'UOM'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'MEINS'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '4'.
HEADER-SELTEXT_L = 'ROL'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'MINBE'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '5'.
HEADER-SELTEXT_L = 'STORAGE'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'LGORT'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '6'.
HEADER-SELTEXT_L = 'WAREHOUSE'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'LGNUM'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '7'.
HEADER-SELTEXT_L = 'PO NUMBER'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'EBELN'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '8'.
HEADER-SELTEXT_L = 'PO LINE#'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'EBELP'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '9'.
HEADER-SELTEXT_L = 'PO QUANTITY'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'DQT'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '10'.
HEADER-SELTEXT_L = 'PR NUMBER'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'BANFN'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '11'.
HEADER-SELTEXT_L = 'PR QUANTITY'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'MENG2'.
APPEND HEADER TO BODY.
CLEAR HEADER.
ENDFORM. " FIELDCATALOG
*&      FORM ALVDISPLAY
      TEXT
FORM ALVDISPLAY.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
   EXPORTING
        I_CALLBACK_PROGRAM      = 'Z_R_CONSUMABLEROL1'
           I_CALLBACK_TOP_OF_PAGE   = 'TOP-OF-PAGE' "SEE FORM
           I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
           I_GRID_TITLE           = OUTTEXT
        IS_LAYOUT               = GD_LAYOUT
        IT_FIELDCAT             = BODY
           IT_SPECIAL_GROUPS       = GD_TABGROUP
           IT_EVENTS                = GT_XEVENTS
        I_SAVE                  = 'X'
           IS_VARIANT              = Z_TEMPLATE
         TABLES
        T_OUTTAB                = ITAB
   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.                    "ALVDISPLAYENDLOOP.
Thanks
Pari

Hi Hari,
I have a preference for one of the work-arounds. No conversion should be necessary. The reason for being so careful is that table conversion (t/code SE14) is bypassing the SAP BW application layer. Normally you create your data model (incl. InfoObjects) in BW and during activation BW requests the ABAP layer to create/change/delete the ABAP Data Dictionary objects. If something goes wrong or needs conversion using ABAP tools, it might lead to unexpected issues/inconsistencies in the future.
One issue I faced was that space occupation of an InfoCube was disrupted. It is too long ago to remember the details and it occurred in an SAP BW 2.0B system.
Anyway, if you read SAP Note 579342 - Changing key figures that are used in InfoProviders it should be possible to go ahead with your approach. Table conversion will have to place in every target system, Please note that according to SAP Note 1248769 - Inconsistency between database and ABAP Dictionary table conversion should be done using user-id DDIC.
Best regards,
Sander

Error in creating Table Maintenance for TABLES: J_2IRG1BAL ,Dump error show

Dear Gurus
I have Created one Table Maintenance for TABLES: J_2IRG1BAL ,
1) I have take function group as same as table name like J_2IRG1BAL
3) Authorization Group &NC&
4) Authorization object S_TABU_DIS
5) Function group J_2IRG1BAL
6) Package J1I5
7) Maintenance type one step.
8) Maint. Screen No.    Overview screen 2009.
9) Recording routine STD recording routines .
I have assign screen single screen 1 but it will not take the screen so ill put screen 2009 ,the system will not not accept the screen but I proposed to Save and activate the table maintenance generator and created and save the function group ,the table is ready to save the entries
We have to go to SM30 then put 4-5 entries ,after that a dump error shows
Which i have attachéd in this mail kindly help me out
Its effect in production server.
I have found that the error is given below I have mentioned all the details
Kindly read this
I have created function group J_2IRG1BAL and assign Package J1I5 and function group,J1I5 is already a Function group so problem occurs a dump error message displays
Kindly give me the right solution all the Clients are effected
110,100 150,250 these all are effected development clients
300 is prod client this is also affected because I have created a table maintenance generator and send the req to production .
*Dump Error Shows in Production*
Runtime Errors         SYNTAX_ERROR
Date and Time          11.12.2008 09:26:30
What happened?
|    Error in ABAP application program.
Error analysis
In program "SAPLJ1I5 ", the following syntax error occurred:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
The current ABAP program "SAPLSVIM" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
In program "SAPLJ1I5 ", the following syntax error occurred
in the Include "SAPLJ1I5 " in line 0:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
rigger Location of Runtime Error                                                                 |
Program                                 SAPLSVIM
Include                                 LSVIMU01
Row                                     107
Module type                             (FUNCTION)
|    Module Name                             VIEW_MAINTENANCE
Author and last person to change the Include are:
Author "TTLABAP2 "
Last changed by "TTLABAP2 "
105
Initialisierung des Abgleichsmandanten zum View                     *
106
>>>>>
vim_default_upgr_clnt-viewname = x_header-viewname.
108
vim_default_upgr_clnt-client   = client_for_upgrade.
109
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
| 110|            USING 'VIM_DEFAULT_UPGR_CLNT' 'C' vim_default_upgr_clnt rc.

I have send you all the details regarding the table maintenance generator
error is shown below
                                       I have Created one Table Maintenance for TABLES: J_2IRG1BAL ,
1) I have take function group as same as table name like J_2IRG1BAL
3) Authorization Group &NC&
4) Authorization object S_TABU_DIS
5) Function group J_2IRG1BAL
6) Package J1I5
7) Maintenance type one step.
8) Maint. Screen No.    Overview screen 2009.
9) Recording routine STD recording routines .
I have assign screen single screen 1 but it will not take the screen so ill put screen 2009 ,the system will not not accept the screen but I proposed to Save and activate the table maintenance generator and created and save the function group ,the table is ready to save the entries
We have to go to SM30 then put 4-5 entries ,after that a dump error shows
Which i have attachéd in this mail kindly help me out
Its effect in production server.
I have found that the error is given below I have mentioned all the details
Kindly read this
I have created function group J_2IRG1BAL and assign Package J1I5 and function group,J1I5 is already a Function group so problem occurs a dump error message displays
Kindly give me the right solution all the Clients are effected
110,100 150,250 these all are effected development clients
300 is prod client this is also affected because I have created a table maintenance generator and send the req to production .
                                                                                Runtime Errors         SYNTAX_ERROR
Date and Time          11.12.2008 09:26:30
ShrtText
Syntax error in program "SAPLJ1I5 ".
What happened?
Error in ABAP application program.
The current ABAP program "SAPLSVIM" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
In program "SAPLJ1I5 ", the following syntax error occurred
in the Include "SAPLJ1I5 " in line 0:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
Author and last person to change the Include are:
Author "TTLABAP2 "
Last changed by "TTLABAP2 "
Error analysis
In program "SAPLJ1I5 ", the following syntax error occurred:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
Trigger Location of Runtime Error
Program                                 SAPLSVIM
Include                                 LSVIMU01
Row                                     107
Module type                             (FUNCTION)
Module Name                             VIEW_MAINTENANCE
Source Code Extract
Line
SourceCde
77
TRANSPORTING NO FIELDS.
78
IF sy-subrc NE 0.
79
SELECT SINGLE * FROM tfdir WHERE funcname EQ <function_name>.
80
IF sy-subrc NE 0.
81
RAISE no_editor_function.
82
ELSE.
83
length = strlen( function_name1 ).
84
ASSIGN function_name1(length) TO <function_name>.
85
SELECT SINGLE * FROM tfdir WHERE funcname EQ <function_name>.
86
IF sy-subrc NE 0.
87
RAISE no_database_function.
88
ENDIF.
89
ENDIF.
90
INSERT x_header-viewname INTO alr_checked_views INDEX sy-tabix.
91
ELSE.
92
length = strlen( function_name1 ).
93
ASSIGN function_name1(length) TO <function_name>.
94
ENDIF.
95
96
Initialisierung der RFC-Destination zum View                        *
97
98
FPOOL+4 = X_HEADER-AREA.
99
fpool   = x_header-fpoolname.
100
vim_default_rfc_dest-viewname = x_header-viewname.
101
vim_default_rfc_dest-rfcdest = rfc_destination_for_upgrade.
102
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
103
USING 'VIM_DEFAULT_RFC_DEST' 'C' vim_default_rfc_dest rc.
104
105
Initialisierung des Abgleichsmandanten zum View                     *
106
>>>>>
vim_default_upgr_clnt-viewname = x_header-viewname.
108
vim_default_upgr_clnt-client   = client_for_upgrade.
109
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
110
USING 'VIM_DEFAULT_UPGR_CLNT' 'C' vim_default_upgr_clnt rc.
111
112
set flag if complex selection conditions in sellist                  *
113
114
IF complex_selconds_used NE space.
115
READ TABLE dba_sellist INDEX 1.
116
IF sy-subrc EQ 0 AND dba_sellist-cond_kind EQ space.
117
dba_sellist-cond_kind = 'C'. MODIFY dba_sellist INDEX 1.
118
ENDIF.
119
ENDIF.
120
121
direkter Vergleich: Flagge setzen usw.                              *
122
123
IF view_action EQ vim_direct_upgrade.
124
view_action = aendern.
125
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
126
USING 'VIM_SPECIAL_MODE' 'C' vim_direct_upgrade rc.

Dump error in mb1a(SAPSQL_ARRAY_INSERT_DUPREC)

Dear Friends,
                       We got a dump error(SAPSQL_ARRAY_INSERT_DUPREC)
                       when relesing particular material of the production order in mb1a. the detail error is as follows.
ABAP runtime errors    SAPSQL_ARRAY_INSERT_DUPREC
"SAPSQL_ARRAY_INSERT_DUPREC"
"SAPLIEP1 " or "LIEP1U04 "
"REMAINDER_OF_EQUI_POST"
SAP Release.............. "46C"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "8x Intel 80686"
Database type............ "ORACLE"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "46D"
Created on............... "Jul 10 2006 21:36:37"
Created in............... "NT 4.0 1381 Service Pack 6 x86 MS VC++ 12.00"
Database version......... "OCI_920_SHARE__OCI_7_API "
Patch level.............. "2257"
Patch text............... " "
Transaction......... "MB1A "
000010   FUNCTION REMAINDER_OF_EQUI_POST.
000020   *"
000030   ""Verbuchungsfunktionsbaustein:
000040   *"
000050   ""Lokale Schnittstelle:
000060   *"       TABLES
000070   *"              SEREQUZ STRUCTURE EQUZ
000080   *"              SERILOA STRUCTURE ILOA
000090   *"              SEREQKT STRUCTURE EQKT
000100   *"
000110   DATA: RECORDS_POST LIKE SY-DBCNT.
000120   * Anzahl der zu verbuchenden Sätze fest
000130     DESCRIBE TABLE SEREQUZ LINES RECORDS_
000140
000150   * Zeitsegmente hinzufügen
000160
     >     INSERT EQUZ FROM TABLE SEREQUZ.
please let me know if you know the solution.
Thanks and Regards,
Shans.

Go to transaction code OMBT, click view "Intervals" and make sure the number range for previous fiscal year and current fiscal year is not clashing.
for example:
Year        From Number   To Number      Current Number
2010     4900000000     4999999999     5000533839
2011      5000000000     5999999999     5000135509
In the above case it will give this dump SAPSQL_ARRAY_INSERT_DUPREC. There may be other reason also.
You can also follow this method
Go to T-code SE16N and input table name MKPF.
Step find: Find the highest material document number.
Go to T-code SNUM or SNRO.and Input object MATBELEG ( direct OMBT)
Click on 'Number ranges' button.
Click on 'Intervals' button.
Check 'Current number'
Now compare it with the highest material document number of STEP FIND.
Change 'Current number' to a higher number.
From my experience this normally happens when number ranged is transported from DEV to PRD accidentally during some IMG config.

ABAP Dump: Error when attempting to IMPORT object "MC02M_0ITM_TAB".

Hi All,
We Enhanced the Data Source 2LIS_02_ITM by adding 2 Fields and then Migrated to Prod. Initially Transports are moved by mistake by Migration without clearing the outbound queue (LBWQ). So V3 Jobs started failing. For this we deleted all the LUW in LBWQ and then executed V3 and it went fine with out any error. And its been 4days that we dont have any failure with V3 Updates.
Now we have one more issue with V1 Update.
We are getting Dump when user is trying to update or create the records.
This is the dump error message.
" An exception occurred that is explained in detail below.
This exception cannot be caught in the context of the current statement.
The reason for the exception is:
When importing the object "MC02M_0ITM_TAB", the component no. 100 in the
dataset has a different type from the corresponding component
of the target object in the program "SAPLMCEX".
The data type is "P" in the dataset, but "C" in the program."
Have anyone of you faced this issue. Please give me the solution what to do. I got SAP Note for this 328181
Please help me with above issue.
Regards
RK

Forgot to add this Info in my previous thread.
Information on where terminated
    Termination occurred in the ABAP program "SAPLMCEX" - in "MCEX_UPDATE_02_V1".
    The main program was "RSM13000 ".
    In the source code you have the termination point in line 1
    of the (Include) program "LMCEXU55".
    The program "SAPLMCEX" was started in the update system.

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

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

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.

Short Dump error while loading data from R/3 to ODS

Hello,
while trying to load data into the ODS from R/3 I get the following short dump error message. How do I carry out step 1 in the below procedure. Where do i find the Activate Function. And idea?
Thanks,
SD
                                                                                Diagnosis
Form routine CONVERT_ITAB_RFC is incorrect in transfer program
     GP4C0LOLZ6OQ70V8JR365GWNW3K .
System Response
The IDoc processing was terminated and indicated as incorrect. The IDoc
     can be reimported at any time.
Procedure
1. Go to the transfer rule maintenance for your InfoSource
         ZFIN_TR_FLQITEM_FI and the source system DA_M_10 and regenerate the
         transfer program using the function Activate. Remove possible syntax
         errors on the basis of your conversion routines.
2. Restart the processing of this IDoc.
3. If the error occurs again search for SAPNet R/3 notes, and create a
        problem message if necessary.
Edited by: Sebastian D'Souza on Jan 13, 2009 3:22 PM

Hi.......
Goto RSA1>> then to source system tab (on left side) >> double click on the desired source system...........Then on the right side you have the Datasource tree..........there search the datasource and activate.......Also u can Replicate the datasource again.......and activate the Transfer rules using the program : RS_TRANSTRU_ACTIVATE_ALL
After this operation when come back to source system (R/3).........I think the error log line will be disappeared from SM58......... Then repeat the load.........
Also u can try to Activate the infosource once...........in RSA1.........before repeating the load....
Hope this helps......
Regards,
Debjani....

Regarding Transport dump error

Similar Messages

Maybe you are looking for