Error in ABAP table

Hi,
I am executing script logic in SAP BPC. however it's back end is SAP BI and i am getting this following error
"A dump error occourred in ABAP stack". while i have tried to pull error info by going through ST22, i can see this below error.
The current ABAP program "CL_UJK_RUN_LOGIC==============CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"BADI_UJ_CUSTOM_LOGIC==========CP " in include
"BADI_UJ_CUSTOM_LOGIC==========CM000 " in
line 9:
"The specified type cannot be converted into the target variables."
The include has been created and last changed by:
Created by: "DDIC "
Last changed by: "DDIC "
Error in the ABAP Application Program
The current ABAP program "CL_UJK_RUN_LOGIC==============CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed
Any advices.

Hi,
The easiest way to debug custom BPC BADI is to put a break point in you BADI and run script that calls it from transaction UJKT.
if you want to debug any script logic run it from UJKT as well and put your break-point in Method RUNLOGIC of Class CL_UJK_RUN_LOGIC. Methods PREPROCESS_LGF, GENERATE_LGX and EXECUTE_LGX process different steps of script execution.
If you can't run your script in UJKT, than you can debug it from DM Package. Scott's blog at /people/scott.cairncross/blog/2010/03/14/troubleshooting-bpc-netweaver-data-manager-packages is an excellent guide to that.
Prabhudas

Similar Messages

  • Abap tables for adapter engine errors

    Hello,
    Which ABAP tables in PI will have the data relating to adapter engine errors (like the communication channel errors). Is there any way I can get the adapter engine errors from abap tables?
    Any help is very much appreciated.
    Thanks
    MLS

    Hello,
    What I am trying to do is write a report in ABAP, which will read the table for errors (for messages which are not processed successfully in Integration engine or adapter engine) and email those errors to users. If there is communication channel error in RWB, the message in sxmb_moni is still shown as success and is not being updated in table SXMSPERROR.
    We cannot use PI Alerts here since the email list is dynamic for the same PI interface.
    Any ideas on how to accomplish this?
    Thanks
    MLS

  • Error "Error in ABAP statement when processing an internal table. table."

    Hello,
    I am facing the error when tried for GR from SRM portal for my shopping cart and for others created shopping cart. The error is
    "Error in ABAP statement when processing an internal table. table."
    I have the central receipient role. Couold any body assist me?
    Thanks,
    Pijush

    Hi Harish,
    Execute the query in RSRT and check whether you have any short dump is in ST22. This would give a clear idea at what might have gone wrong.
    Another thing is to check whether the code for the variable is fine in the user exit.
    Hope this helps.
    Bye
    Dinesh

  • Runtime error in abap report

    error analysis as in ST22 TRANSACTION:
    AN EXCEPTION OCCURED THE EXCEPTION ASSIGNED TO CLASS CX_SY_CONVERSION_NO_NUMBER WAS NOT CAUGHT WHICH LED TO AN ERROR. THE REASON FOR THIS EXCEPTION IS :
    THE PROGRAM TRIED TO INTERPRET VALUE ':4' AS NUMBER SINCE THE VALUE CONTRAVENES THE CORRECT NUMBER FORMAT THIS WAS NOT POSSIBLE.
    ATTACHED IS MY PROGRAM
    REPORT ZVXR0303
          LINE-COUNT 60(3)
          LINE-SIZE 132
           MESSAGE-ID VN.
    Tables: VBEP, VBAP, NAST.
    DATA: BEGIN OF HEADER,
          ORDER(15) VALUE  'ORDER',
           LINE(5)  VALUE  'LINE',
      MATERIAL(14)  VALUE  'MATERIAL',
           DUE(15)  VALUE  'DUE (MAD)',
       CREATED(10)  VALUE  'CREATED',
           QTY(10)  VALUE  'QUANTITY',
            KEY(5)  VALUE  'KEY',
           TYPE(5)  VALUE  'TYPE',
           END OF HEADER.
    DATA: Begin of IDAT OCCURS 0,
      VBELN         LIKE VBAP-VBELN,
      POSNR         LIKE VBAP-POSNR,
      werks         LIKE VBAP-WERKS,
      cuobj         LIKE vbap-CUOBJ,
      MBDAT         LIKE vbep-mbdat,
      ERDAT         LIKE VBAP-ERDAT,
      MATNR         LIKE VBAP-MATNR,
      KWMENG        LIKE VBAP-KWMENG,
      QTY           TYPE I,
      END of IDAT.
    class cl_abap_char_utilities definition load.
    constants: tab type c value cl_abap_char_utilities=>HORIZONTAL_TAB.
    DATA: t_record(1000) TYPE C.
    DATA: C_KWMENG(20)   TYPE C.
    data: OUTFILE(50) value '/usr/users/ftpsapfi/locks_540318'.
    DATA: BEGIN OF TKOMCON OCCURS 50.
            INCLUDE STRUCTURE CONF_OUT.
    DATA: END   OF TKOMCON.
    DATA: iKEY         TYPE I,
          offset       TYPE I,
          KeyTypeLOC   TYPE I,
          KeyNumberLOC TYPE I,
          type(15)     TYPE C.
        select-options: sVBELN FOR VBEP-VBELN obligatory,
                        sMAD FOR VBEP-MBDAT obligatory,
                        sERDAT FOR VBAP-ERDAT,
                        sMATNR FOR VBAP-MATNR,
                        sWERKS FOR VBAP-WERKS,
                        sKWMENG FOR VBAP-KWMENG.
    SELECT
      vbap~vbeln
      vbap~POSNR
      vbap~werks
      vbap~cuobj
      VBEP~MBDAT
      VBAP~ERDAT
      VBAP~MATNR
      VBAP~KWMENG
    INTO CORRESPONDING FIELDS of IDAT
    FROM ( VBEP INNER JOIN VBAP ON vbepvbeln = vbapvbeln
    AND vbepposnr = vbapposnr )
    WHERE BMENG > 0
    AND vbep~MBDAT IN sMAD
    AND VBEP~VBELN in sVBELN
    AND VBAP~werks IN sWERKS
    AND VBAP~ERDAT IN sERDAT
    AND VBAP~MATNR IN sMATNR
    AND VBAP~KWMENG IN sKWMENG
    AND VBAP~ABGRU = SPACE.
      APPEND IDAT.
    ENDSELECT.
    PERFORM TOP-OF-PAGE.
    if sy-batch = 'x'.
    OPEN DATASET OUTFILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
    TRANSFER t_record  TO OUTFILE.
    endif.
    IF SY-SUBRC = 0.
      LOOP at IDAT.
       write IDAT-KWMENG DECIMALS 0 TO C_KWMENG.
        REFRESH TKOMCON.
        CALL FUNCTION 'VC_I_GET_CONFIGURATION'
             EXPORTING
                  INSTANCE      = idat-cuobj
                  LANGUAGE      = NAST-SPRAS
             TABLES
                  CONFIGURATION = TKOMCON
             EXCEPTIONS
                  OTHERS        = 4.
        LOOP AT TKOMCON
          WHERE ATNAM = 'S_SK_SPEC_KEY' OR ATNAM = 'S_MK_SPEC_KEY'
          OR ATNAM = 'S_SK_CONSC_KEY' OR ATNAM = 'S_MK_CONSC_KEY'.
          IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
          OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
            KeyTYPELOC = 0.
            keynumberloc = 2.
            TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
            IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
              iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
              IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
              OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
                PERFORM OUT-OF-RANGE-FOUND.
              ENDIF.
            ENDIF.
          Else.
            Offset = 0.
            DO.
              IF offset <= 9.
                offset = offset + 1.
                If TKOMCON-ATWRT+Offset(1) = ':'.
                  KeyTypeLOC = Offset + 1.
                  KeyNumberLOC = Offset + 3.
                  EXIT.
                ENDIF.
              ELSE.
                EXIT.
              ENDIF.
            ENDDO.
            TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
            IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
              iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
              IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
              OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
                IDAT-KWMENG = TKOMCON-ATWRT(3).
                PERFORM OUT-OF-RANGE-FOUND.
              ENDIF.
            ENDIF.
          ENDIF.
        ENDLOOP.
      ENDLOOP.
    ENDIF.
    CLOSE DATASET OUTFILE.
          FORM OUT-OF-RANGE-FOUND                                       *
    FORM OUT-OF-RANGE-FOUND.
      WRITE: / IDAT-VBELN.
      WRITE: 10 IDAT-POSNR.
      WRITE: 20 IDAT-MATNR.
      WRITE: 35 IDAT-MBDAT.
      WRITE: 50 IDAT-ERDAT.
      WRITE: 65(3) IDAT-KWMENG DECIMALS 0.
      WRITE: 75 TKOMCON-ATWRT+KeyTypeLOC(6).
      IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
         OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
        WRITE: 85 'Consecutive'.
      ELSE.
        WRITE: 85 'Specific'.
      ENDIF.
      IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
         OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
        TYPE = 'Consecutive'.
      ELSE.
        TYPE = 'Specific'.
      ENDIF.
    * PREPARING A RECORD TO BE SENT TO FILE
      CONCATENATE
      IDAT-VBELN
      IDAT-POSNR
      IDAT-MATNR
      IDAT-MBDAT
      IDAT-ERDAT
      C_KWMENG
      TKOMCON-ATWRT+KeyTypeLOC(6)
      TYPE
      INTO t_record SEPARATED BY tab.
      if sy-batch = 'x'.
      TRANSFER t_record  TO OUTFILE.
      endif.
    ENDFORM.
          FORM TOP-OF-PAGE                                              *
    FORM TOP-OF-PAGE.
      WRITE: / 'ORDER'.
      WRITE: 10 'LINE'.
      WRITE: 20 'MATERIAL'.
      WRITE: 35 'DUE (MAD)'.
      WRITE: 50 'CREATED'.
      WRITE: 65 'QTY'.
      WRITE: 75 'KEY'.
      WRITE: 85 'TYPE'.
    PREPARING A RECORD TO BE SENT TO FILE
      CONCATENATE
      header-ORDER
      header-LINE
      header-MATERIAL
      header-DUE
      header-CREATED
      header-QTY
      header-KEY
      header-TYPE
      INTO t_record SEPARATED BY tab.
    ENDFORM.
    THIS IS WORKING FINE WITH DIFFERENT RANGES BUT WHEN I USE RANGE
    Sales Order 1250000 TO 2250000
    MAD 01/18/2005 TO 03/02/2005
    Material LOCK9250FR TO LOCK9250XF
    PLANT 4500
    IT GIVES THE RUNTIME ERROR I MENTIONED ABOVE
    ANY HELP WOULD BE GREATLY APPRECIATED
    THANKS.

    HI ROB YOUR REPLY LOOKS TO BE VERY CLOSE OTHER GUYS SAID IT MIGHT BE PROBLEM WITH VARIABLE C_KWMENG BUT I REMOVED THAT PIECE OF CODE WITH C_KWMENG BUT STILL I WAS GETTING THE ERROR ATTACHED IS THE COMPLETE ERROR DETAILS FROM ST22
    Runtime Errors         CONVT_NO_NUMBER              
    Exception              CX_SY_CONVERSION_NO_NUMBER
           Occurred on     09/29/2005 at 14:33:21
    Unable to interpret "04:" as a number.                                        
    What happened?
    Error in ABAP application program.                                                                               
    The current ABAP program "ZVXR0303" 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.                                                                               
    Error analysis
    An exception occurred. This exception will be dealt with in more detail                  
    below. The exception, assigned to the class 'CX_SY_CONVERSION_NO_NUMBER', was            
    not caught, which                                                                       
    led to a runtime error. The reason for this exception is:                               
    The program attempted to interpret the value "04:" as a number, but                      
    since the value contravenes the rules for correct number formats,                        
    this was not possible.                                                                               
    How to correct the error
    Integers are represented in ABAP using a sequence of digits and, in some                 
    cases, a preceding sign.                                                                
    The system offers the following options for displaying floating point                    
    numbers:                                                                               
    [mantissa]E[sign][exponent]                                                      
      [whole number part].[fractional part]                                            
    e.g. -12E+34, +12E-34, 12E34, 12.34                                                                               
    If the error occurred in one of your own programs or in an SAP program                   
    that you modified, try to correct it yourself.                                                                               
    You may able to find an interim solution to the problem                                  
    in the SAP note system. If you have access to the note system yourself,                  
    use the following search criteria:                                                                               
    "CONVT_NO_NUMBER" CX_SY_CONVERSION_NO_NUMBERC                                            
    "ZVXR0303" or "ZVXR0303"                                                                 
    "START-OF-SELECTION"                                                                     
    If you cannot solve the problem yourself, please send the                                
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                             
       To obtain this, select the "Print" function on the current screen.                    
                                                                                    2. A suitable hardcopy prinout of the system log.                                        
       To obtain this, call the system log with Transaction SM21                             
       and select the "Print" function to print out the relevant                             
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,                       
       supply the source code.                                                               
       To do this, you can either use the "PRINT" command in the editor or                   
       print the programs using the report RSINCL00.                                                                               
    4. Details regarding the conditions under which the error occurred                       
       or which actions and input led to the error.                                          
    System environment
    SAP Release.............. "620"                                                                               
    Application server....... "grrsap54"                                                     
    Network address.......... "10.80.96.102"                                                 
    Operating system......... "HP-UX"                                                        
    Release.................. "B.11.11"                                                      
    Hardware type............ "9000/800"                                                     
    Character length......... 8 Bits                                                         
    Pointer length........... 64 Bits                                                        
    Work process number...... 3                                                              
    Short dump setting....... "full"                                                                               
    Database server.......... "grrsap54"                                                     
    Database type............ "ORACLE"                                                       
    Database name............ "D01"                                                          
    Database owner........... "SAPR3"                                                                               
    Character set............ "en_US.iso88591"                                                                               
    SAP kernel............... "640"                                                          
    Created on............... "Aug 28 2005 20:25:49"                                         
    Created in............... "HP-UX B.11.00 A 9000/800"                                     
    Database version......... "OCI_920 "                                                                               
    Patch level.............. "88"                                                           
    Patch text............... " "                                                                               
    Supported environment....                                                                
    Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE                    
    10.1.0.."                                                                             
    SAP database version..... "640"                                                          
    Operating system......... "HP-UX B.11"                                                   
    User, transaction...
    Client.............. 050                                                                 
    User................ "NSHAKER"                                                           
    Language key........ "E"                                                                 
    Transaction......... "SE38 "                                                             
    Program............. "ZVXR0303"                                                          
    Screen.............. "SAPMSSY0 1000"                                                     
    Screen line......... 6                                                                   
    Information on where terminated
    The termination occurred in the ABAP program "ZVXR0303" in                               
    "START-OF-SELECTION".                                                                   
    The main program was "ZVXR0303 ".                                                                               
    The termination occurred in line 156 of the source code of the (Include)                 
    program "ZVXR0303"                                                                      
    of the source code of program "ZVXR0303" (when calling the editor 1560).                 
    Source code extract
    Caution: Program has changed            
    Caution: At time of termination,  Active source code no longer available
    001260 ?         TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.            
    001270 ?         IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.             
    001280 ?           iKey = TKOMCON-ATWRT+KeyNumberLOC(4).                        
    001290 ?                                                                        
    001300 ?           IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )    
    001310 ?           OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).  
    001320 ?             PERFORM OUT-OF-RANGE-FOUND.                                
    001330 ?           ENDIF.                                                       
    001340 ?         ENDIF.                                                         
    001350 ?       Else.                                                            
    001360 ?         Offset = 0.                                                    
    001370 ?         DO.                                                            
    001380 ?           IF offset <= 9.                                              
    001390 ?             offset = offset + 1.                                       
    001400 ?             If TKOMCON-ATWRT+Offset(1) = ':'.                          
    001410 ?               KeyTypeLOC = Offset + 1.                                 
    001420 ?               KeyNumberLOC = Offset + 3.                               
    001430 ?               EXIT.                                                    
    001440 ?             ENDIF.                                                     
    001450 ?           ELSE.                                                        
    001460 ?             EXIT.                                                      
    001470 ?           ENDIF.                                                       
    001480 ?         ENDDO.                                                         
    001490 ?                                                                        
    001500 ?         TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.            
    001510 ?                                                                        
    001520 ?         IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.             
    001530 ?           iKey = TKOMCON-ATWRT+KeyNumberLOC(4).                        
    001540 ?           IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )    
    001550 ?           OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).  
    ?             IDAT-KWMENG = TKOMCON-ATWRT(3).                            
    001570 ?             PERFORM OUT-OF-RANGE-FOUND.                                
    001580 ?           ENDIF.                                                       
    001590 ?         ENDIF.                                                         
    001600 ?       ENDIF.                                                           
    001610 ?     ENDLOOP.                                                           
    001620 ?   ENDLOOP.                                                             
    001630 ? ENDIF.                                                                 
    001640 ? CLOSE DATASET OUTFILE.                                                 
    001650 ?                                                                        
    001660 ? *----
    001670 ? *       FORM OUT-OF-RANGE-FOUND                                       *
    001680 ? *----
    001690 ? *       ........                                                      *
    001700 ? *----
    001710 ? FORM OUT-OF-RANGE-FOUND.                                               
    001720 ?                                                                        
    001730 ?   WRITE: / IDAT-VBELN.                                                 
    001740 ?   WRITE: 10 IDAT-POSNR.                                                
    001750 ?   WRITE: 20 IDAT-MATNR.                                                
    Contents of system fields
    SY field contents..................... SY field contents.....................
    SY-SUBRC 0                             SY-INDEX 44                           
    SY-TABIX 7                             SY-DBCNT 1                            
    SY-FDPOS 4                             SY-LSIND 0                            
    SY-PAGNO 2                             SY-LINNO 18                           
    SY-COLNO 94                            SY-PFKEY                              
    SY-UCOMM                               SY-TITLE Out of Range Keys            
    SY-MSGTY I                             SY-MSGID SF                           
    SY-MSGNO 616                           SY-MSGV1                              
    SY-MSGV2                               SY-MSGV3                              
    SY-MSGV4                              
    Active calls / events
    No.... Type........ Name..........................
           Program                                
           Include                                  Line    
           Class                                  
         1 EVENT        START-OF-SELECTION                                          
           ZVXR0303                               
           ZVXR0303                                   156
    Chosen variables
         1 EVENT        START-OF-SELECTION                                          
           ZVXR0303                               
           ZVXR0303                                   156
    %_SPACE                                                                               
    2                                      
                                   0                                      
    SY-REPID                       ZVXR0303                               
                                   5555333322222222222222222222222222222222
                                   A682030300000000000000000000000000000000
    TKOMCON-ATWRT                  04:XF1260                              
                                   333543333222222222222222222222         
                                   04A861260000000000000000000000         
    KEYNUMBERLOC                   5                                      
                                   0000                                   
                                   0005                                   
    SYST-REPID                     ZVXR0303                               
                                   5555333322222222222222222222222222222222
                                   A682030300000000000000000000000000000000
    SY-LDBPG                       SAPDB__S                               
                                   5454455522222222222222222222222222222222
                                   31042FF300000000000000000000000000000000
    IKEY                           1260                                   
                                   000E                                   
                                   004C                                   
    KEYTYPELOC                     3                                      
                                   0000                                   
                                   0003                                   
    SY                             ###,####################################
                                   0002000000000001000000000000000000000000
                                   000C00020007000E00000001000A000000000000
    ... +  40                      ###########^###<########################
                                   0000000000050003000100080000000000000009
                                   00010004000E000C000200040000000000000000
    ... +  80                      ########################################
                                   0000000000000000000000000000000000000000
                                   0000000000000000000A00000000000000000000
    ... + 120                      #######################################_
                                   0000000000000000000000000000000000010005
                                   00000000000000000000000000000000000A000F
    ... + 160                      ############ÿÿ¹°XC#############   E2  X1
                                   000000000000FFBB540000000000000222432253
                                   0000000A0000FF90830040000C0000C000520081
    ... + 200                      000         ####__S                 050
                                   3332222222220000555222222222222222223332
                                   0000000000000000FF3000000000000000000500
    ... + 240                           00                                
                                   222223322222222                        
                                   000000000000000                        
    SVBELN                         IBT00012500000002250000                
                                   44533333333333333333333                
                                   92400012500000002250000                
    IDAT-KWMENG                    ########                               
                                   00000000                               
                                   0000000C                               
    TKOMCON-ATWRT+0(3)             04:                                    
                                   333                                    
                                   04A                                    
    SYST                           ###,####################################
                                   0002000000000001000000000000000000000000
                                   000C00020007000E00000001000A000000000000
    ... +  40                      ###########^###<########################
                                   0000000000050003000100080000000000000009
                                   00010004000E000C000200040000000000000000
    ... +  80                      ########################################
                                   0000000000000000000000000000000000000000
                                   0000000000000000000A00000000000000000000
    ... + 120                      #######################################_
                                   0000000000000000000000000000000000010005
                                   00000000000000000000000000000000000A000F
    ... + 160                      ############ÿÿ¹°XC#############   E2  X1
                                   000000000000FFBB540000000000000222432253
                                   0000000A0000FF90830040000C0000C000520081
    ... + 200                      000         ####__S                 050
                                   3332222222220000555222222222222222223332
                                   0000000000000000FF3000000000000000000500
    ... + 240                           00                                
                                   222223322222222                        
                                   000000000000000                        
    OUTFILE                        /usr/users/ftpsapfi/locks_540318       
                                   2777277677267776766266667533333322222222
                                   F532F53523F64031069FCF3B3F54031800000000
    ... +  40                                                                               
    2222222222                             
                                   0000000000                             
    Application Calls
    No dump information available                    
    Application Information
    No dump information available                    
    Internal notes
    The termination occurred in the function "ab_Move" of the SAP                            
    Basis System, specifically in line 529 of the module                                     
    "//bas/640_REL/src/krn/runt/abmove1.c#6".                                               
    The internal operation just processed is "MOVE".                                         
    The internal session was started at 20050929142552.                                      
    Active calls in SAP kernel
    ( 0)  0x4000000001751924   CTrcStack2 + 0x2bc  dw.sapD01_DVEBMGS00                    
    ( 1)  0x4000000001751658   CTrcStack + 0x18  dw.sapD01_DVEBMGS00                      
    ( 2)  0x4000000001db7478   rabax_CStackSave__Fv + 0x100  dw.sapD01_DVEBMGS00          
    ( 3)  0x4000000001dc3abc   ab_rabax + 0x1e1c  dw.sapD01_DVEBMGS00                     
    ( 4)  0x4000000001b44cb4   ab_cnverr__FiPcPCvN21T2 + 0x18c  dw.sapD01_DVEBMGS00       
    ( 5)  0x40000000016c96f8   ab_Move + 0x1910  dw.sapD01_DVEBMGS00                      
    ( 6)  0x40000000016d4434   ab_jmove__Fv + 0x384  dw.sapD01_DVEBMGS00                  
    ( 7)  0x4000000001022348   ab_extri__Fv + 0x17a0  dw.sapD01_DVEBMGS00                 
    ( 8)  0x4000000001726dc8   ab_xevent__FPCc + 0x38  dw.sapD01_DVEBMGS00                
    ( 9)  0x40000000019f7efc   ab_trigg__Fv + 0x94  dw.sapD01_DVEBMGS00                   
    (10)  0x40000000019dc9ec   ab_run + 0xc4  dw.sapD01_DVEBMGS00                         
    (11)  0x4000000000f65e0c   N_ab_run + 0x14  dw.sapD01_DVEBMGS00                       
    (12)  0x4000000000f5fa88   dynpmcal + 0x198  dw.sapD01_DVEBMGS00                      
    (13)  0x4000000000f5d500   dynppai0 + 0x830  dw.sapD01_DVEBMGS00                      
    (14)  0x4000000000f5b8b4   dynprctl + 0x43c  dw.sapD01_DVEBMGS00                      
    (15)  0x4000000000f56728   dynpen00 + 0x2118  dw.sapD01_DVEBMGS00                     
    (16)  0x400000000102f1b4   Thdynpen00 + 0x69c  dw.sapD01_DVEBMGS00                    
    (17)  0x400000000102e1e4   TskhLoop + 0x523c  dw.sapD01_DVEBMGS00                     
    (18)  0x4000000001022f50   tskhstart + 0x1e0  dw.sapD01_DVEBMGS00                     
    (19)  0x4000000000dce3c4   DpMain + 0x484  dw.sapD01_DVEBMGS00                        
    (20)  0x40000000022784cc   nlsui_main + 0x14  dw.sapD01_DVEBMGS00                     
    (21)  0x4000000000a39534   main + 0x14  dw.sapD01_DVEBMGS00                           
    (22)  0xc00000000000a588   $START$ + 0xa0  /usr/lib/pa20_64/dld.sl                    
    List of ABAP programs affected
    Type  Program                            Gen. Date  Time       Load Size 
    Prg   ZVXR0303                           09/29/2005 14:25:42       39936 
    Prg   SAPMSSY0                           05/01/2005 00:21:19       66560 
    Prg   SAPMSSYD                           06/05/2002 17:09:33       16384 
    Prg   SAPFSYSCALLS                       02/14/2002 14:22:47        6144 
    Prg   RSDBRUNT                           06/13/2004 00:43:20      226304 
    Typ   RSSCR                                /  /       : m:15        5120 
    Prg   RSDBSPBL                           01/07/2003 18:47:02       59392 
    Prg   SAPDB__S                           02/14/2002 14:22:47       15360 
    Typ   VARID                              05/12/1997 16:51:30        4096 
    Prg   %_CSYDB0                           02/14/2002 14:22:46       28672 
    Prg   RSDBSPVA                           09/06/2005 22:54:22      112640 
    Prg   SAPLSVAR                           09/06/2005 22:57:28      625664 
    Typ   VARIS                              05/12/1997 15:27:21        2048 
    Typ   RSVAMEMKEY                         05/07/1997 13:07:49        2048 
    Prg   RSDBSPMC                           06/05/2002 17:09:26       66560 
    Typ   DDSHDESCR                          09/03/1997 03:05:16        3072 
    Typ   SPPARAMS                           05/07/1997 13:10:38        2048 
    Typ   SPPARAMS                           05/07/1997 13:10:38        2048 
    Typ   RSSELINT                           04/04/1995 16:12:37        2048 
    Prg   SAPLICON                           03/12/2004 06:57:52       23552 
    Prg   %_CICON                            02/14/2002 14:22:46       65536 
    Prg   SAPLSABE                           02/14/2002 14:22:47       11264 
    Prg   SAPLSECU                           05/23/2005 14:04:05       64512 
    Typ   RSSUBINFO                          10/14/1999 22:01:03        3072 
    Prg   %_CRSDS                            02/14/2002 14:22:46        8192 
    Typ   RSDSEXPR                           08/20/1998 10:57:18        2048 
    Prg   SAPLDSYA                           02/14/2002 14:22:47       39936 
    Prg   SAPFSDS1                           01/07/2003 18:32:17       47104 
    Typ   TDCLD                              11/02/1998 09:51:35        5120 
    Prg   SAPLSDOD                           04/30/2005 22:53:50       39936 
    Typ   DOKIL                              05/12/1997 16:46:17        3072 
    Prg   SAPCNVE                            02/14/2002 14:22:47        6144 
    Prg   SAPLLANG                           02/14/2002 14:22:47        8192 
    Typ   T002                               02/14/1998 10:24:58        2048 
    Typ   RSEXFCODE                          08/13/1997 12:52:57        1024 
    Prg   SAPFSPOR                           03/13/2004 19:20:44       12288 
    Prg   SAPLOMCV                           05/01/2005 00:14:10       16384 
    Prg   CL_EXITHANDLER================CP   06/13/2004 00:40:58       26624 
    Prg   SAPLSEXV                           09/06/2005 22:55:26      107520 
    Prg   CL_BADI_FLT_DATA_TRANS_AND_DB=CP   05/01/2005 00:21:35       33792 
    Typ   SXS_ATTR                           08/20/2001 12:23:27        4096 
    Typ   V_EXT_ACT                          11/09/2000 14:27:05        2048 
    Typ   SXC_EXIT                           11/09/2000 14:23:43        2048 
    Prg   CL_EX_BADI_MATN1==============CP   05/01/2005 00:14:04       22528 
    Prg   IF_EX_BADI_MATN1==============IP   06/13/2004 00:48:55        4096 
    Typ   TMCNV                              02/24/1999 03:33:25        3072 
    Prg   SAPLSCNT                           02/14/2002 14:22:47       24576 
    Typ   DYCBOX                             08/20/1998 11:16:53        2048 
    Prg   SAPLSVSM                           01/07/2003 18:35:45       22528 
    Prg   SAPLSGUI                           01/09/2003 17:15:12       31744 
    Prg   SAPLSTTM                           05/01/2005 00:24:04       75776 
    Prg   SAPLSBDC                           05/23/2005 14:05:19       38912 
    Prg   CL_DATAPROVIDER===============CP   02/14/2002 14:22:46       40960 
    Prg   %_CCNTL                            02/14/2002 14:22:46       13312 
    Typ   OBJ_RECORD                         02/14/1998 08:30:43        2048 
    Prg   SAPLSTUP                           05/23/2005 14:03:46       65536 
    Prg   SAPLCNDP                           05/23/2005 14:05:47      167936 
    Prg   SAPFGUICNTL                        01/09/2003 17:18:52       20480 
    Prg   SAPLOLEA                           05/23/2005 14:03:56       79872 
    Prg   SAPLSFES                           09/06/2005 22:53:55      191488 
    Prg   SAPLSPLUGIN                        02/14/2002 14:22:48        6144 
    Typ   ARFCRDATA                          11/09/2000 14:04:16        6144 
    Prg   SAPLGRFC                           02/14/2002 14:22:47       13312 
    Typ   SWCBCONT                           11/15/2000 17:55:11        3072 
    Typ   OLE_VERBS                          04/04/1995 16:02:20        2048 
    Typ   OLE_PA                             04/04/1995 16:02:19        2048 
    Prg   SAPSHDTV                           03/12/2004 06:40:27       28672 
    Typ   SSCRTEXTS                          09/03/1997 03:12:33        3072 
    Typ   SSCRFIELDS                         05/13/1997 12:54:26        4096 
    Prg   CL_GUI_PROPS_CONSUMER=========CP   01/07/2003 18:26:56       26624 
    Prg   SAPLTHFB                           09/06/2005 22:52:48      306176 
    Prg   CL_DYNAMIC_GUI_EXTENSIONS=====CP   02/14/2002 14:22:46       33792 
    Prg   CL_GUI_DATAMANAGER============CP   05/01/2005 00:20:36       70656 
    Prg   CL_ABAP_CHAR_UTILITIES========CP   05/01/2005 00:14:49       11264 
    Prg   RSDBSPVD                           05/01/2005 00:15:44       73728 
    Typ   RVARI                              03/30/1998 09:40:50        4096 
    Typ   RSVARIVDAT                         04/04/1995 16:12:54        2048 
    Typ   VBEP                               01/27/2003 16:50:17       10240 
    Typ   VBAP                               09/15/2005 11:15:36       44032 
    Prg   SAPLCEI0                           09/22/2005 14:34:40      936960 
    Typ   API_VALUE                          02/20/1998 08:46:47        2048 
    Prg   SAPLCUEV                           06/07/2001 18:26:56       10240 
    Prg   SAPLSUNI                           06/13/2004 00:42:30      131072 
    Typ   TFDIR                              07/29/1998 19:49:08        3072 
    Prg   %_CIBCO2                           03/13/2004 14:32:13       12288 
    Typ   IBINCOM                            06/01/1999 11:56:27        3072 
    Typ   IBINCONF                           06/01/1999 11:56:27        2048 
    Typ   IBSTCONF                           06/01/1999 11:56:28        1024 
    Prg   SAPLCUCB                           05/23/2005 15:20:17      192512 
    Typ   TCUIBSPECIAL                       06/07/2001 17:50:37        1024 
    Prg   %_CIBXX                            03/13/2004 14:38:45       49152 
    Typ   BAL_S_MSG                          12/04/2000 13:04:01        6144 
    Prg   CX_CBASE_ERROR================CP   01/27/2003 16:58:10       10240 
    Typ   SCX_SRCPOS                         11/09/2000 14:12:15        2048 
    Typ   BAL_S_CONT                         11/02/1998 09:43:07        2048 
    Typ   BAL_S_PARM                         12/04/2000 12:45:14        3072 
    Typ   BAL_S_CLBK                         11/02/1998 09:43:07        2048 
    Prg   CX_STATIC_CHECK===============CP   02/14/2002 14:22:47        8192 
    Prg   CX_ROOT=======================CP   02/14/2002 14:22:47        9216 
    Prg   CL_CBASE======================CP   05/23/2005 15:19:44       87040 
    Typ   T371G                              04/29/1998 10:42:48        2048 
    Prg   SAPLIBCO                           03/13/2004 15:32:40      269312 
    Prg   %_CIBCO                            03/13/2004 14:38:45       11264 
    Prg   SAPLIBXX                           03/13/2004 14:38:46       11264 
    Prg   SAPLIBIBF                          03/13/2004 14:38:46      179200 
    Prg   %_CIBIB                            03/13/2004 14:38:45       18432 
    Prg   SAPLIBINF                          06/12/2004 22:20:22      415744 
    Prg   %_CIBIN                            03/13/2004 15:32:40       48128 
    Prg   CL_IBASE_STRUC================CP   06/07/2001 19:59:10      106496 
    Prg   %_CIBST                            03/13/2004 14:38:45       37888 
    Prg   CL_IBASE_STRUC_BUF============CP   06/07/2001 19:59:10       89088 
    Prg   CL_IBASE_STRUC_STAT===========CP   06/07/2001 19:59:10        8192 
    Prg   CL_IBASE_STRUC_BUF_IBSTREF====CP   06/07/2001 19:59:10       35840 
    Prg   %_CIBCO1                           03/13/2004 14:38:45       14336 
    Typ   IBINVAL                            09/18/2001 10:02:52        2048 
    Prg   SAPLIBCU                           03/13/2004 14:38:46       12288 
    Prg   SAPLIBCUT                          06/07/2001 18:27:19       12288 
    Typ   T371B                              05/14/1998 22:58:43        2048 
    Typ   V_IBINR                            03/13/2004 15:32:40        5120 
    Typ   V_IBINR_CM                         03/13/2004 15:32:40        5120 
    Prg   CL_IBASE_SERVICE==============CP   06/07/2001 19:59:10       13312 
    Prg   CL_IBASE_T371D_BUF============CP   06/07/2001 19:59:10       12288 
    Typ   T371D                              08/27/1999 18:19:44        2048 
    Prg   CL_IBASE_R3_MATERIAL==========CP   05/23/2005 15:08:24       59392 
    Typ   MARA                               05/23/2005 15:08:18       22528 
    Typ   MAKT                               08/28/1997 08:52:19        2048 
    Typ   ICON                               01/03/1996 15:34:02        3072 
    Prg   CL_ABAP_TYPEDESCR=============CP   05/01/2005 00:20:10       21504 
    Prg   CL_ABAP_ELEMDESCR=============CP   05/01/2005 00:20:33       20480 
    Prg   CL_ABAP_DATADESCR=============CP   03/12/2004 07:16:33       14336 
    Prg   CL_ABAP_REFDESCR==============CP   03/12/2004 07:17:23       16384 
    Prg   CL_ABAP_STRUCTDESCR===========CP   05/01/2005 00:20:33       20480 
    Prg   CL_ABAP_COMPLEXDESCR==========CP   03/12/2004 07:16:33       13312 
    Prg   CL_ABAP_TABLEDESCR============CP   03/12/2004 07:17:23       17408 
    Prg   CL_ABAP_CLASSDESCR============CP   03/12/2004 07:17:23       23552 
    Prg   CL_ABAP_OBJECTDESCR===========CP   03/12/2004 07:17:23       25600 
    Prg   CL_ABAP_INTFDESCR=============CP   03/12/2004 07:16:33       19456 
    Prg   CL_ABAP_SOFT_REFERENCE========CP   03/29/2001 16:42:12        7168 
    Prg   CL_ABAP_REFERENCE=============CP   02/14/2002 14:22:46        6144 
    Prg   IF_EX_CM_BADI_VERSION=========IP   01/07/2002 16:09:04        3072 
    Prg   %_CABAP                            01/07/2003 18:31:23       23552 
    Typ   SXS_INTER                          11/30/1998 15:55:16        2048 
    Prg   CL_EX_CM_BADI_VERSION=========CP   05/01/2005 00:14:04       13312 
    Prg   %_CSXRT                            06/13/2004 00:40:55       11264 
    Prg   CL_EXIT_MASTER================CP   06/13/2004 00:40:58       13312 
    Typ   V_EXT_IMP                          11/09/2000 14:27:05        2048 
    Typ   V_EXT_IMP                          11/09/2000 14:27:05        2048 
    Typ   SXC_IMPSWH                         11/09/2000 14:23:44        2048 
    Prg   CL_IM_CM_BADI_VERSION_DEF=====CP   04/17/2002 11:01:00        6144 
    Prg   SAPLASTAT_TRIG                     02/14/2002 14:22:47       11264 
    Typ   ASTAT_TYP2                         11/10/1998 05:35:18        2048 
    Prg   IF_CM_BASELINE================IP   05/23/2005 15:08:24        9216 
    Prg   IF_IBASE_IBOF_TREE_OBJECT=====IP   05/23/2005 15:08:24        5120 
    Prg   IF_IBASE_INSTALL==============IP   06/07/2001 20:08:54        4096 
    Prg   IF_IBASE_MATERIAL=============IP   06/07/2001 20:08:54        3072 
    Prg   IF_IBASE_OBJECT===============IP   06/07/2001 20:08:54        4096 
    Prg   SAPLBOMA                           02/14/2002 14:15:40       10240 
    Typ   IONRA                              03/12/2004 02:09:40       23552 
    Typ   IBIBCOM                            08/30/2001 17:56:57        4096 
    Typ   IBIB                               03/13/2004 14:32:13        5120 
    Prg   CL_IBASE_STRUC_SERVICE========CP   06/07/2001 19:59:10       17408 
    Prg   CL_CU_CBASE_ENQUEUE_CORE======CP   06/07/2001 19:58:59       11264 
    Prg   CL_CU_CBASE_ENQUEUE===========CP   06/07/2001 19:58:59       16384 
    Typ   T371F                              06/01/1999 12:00:49        2048 
    Typ   V_IBIN_SYVAL                       03/13/2004 15:32:41        4096 
    Typ   IBIN                               09/18/2001 10:02:52        6144 
    Typ   IBINOWN                            02/01/2000 14:56:07        2048 
    Prg   CL_IBASE_T371F_BUF============CP   06/07/2001 19:59:11        8192 
    Prg   CL_IBASE_STRUC_FILT_02========CP   06/07/2001 19:59:10       11264 
    Prg   CL_IBASE_STRUC_FILT===========CP   06/07/2001 19:59:10       10240 
    Typ   IBST                               09/18/2001 10:02:52        4096 
    Typ   IBST                               09/18/2001 10:02:52        4096 
    Typ   IBSTREF                            04/15/1998 00:20:43        2048 
    Typ   IBSTREF                            04/15/1998 00:20:43        2048 
    Prg   IF_CBASE_E====================IP   06/07/2001 20:08:25        3072 
    Prg   %_CCXTAB                           02/14/2002 14:22:46        6144 
    Prg   SAPLCUCQ                           09/15/2005 11:15:38       79872 
    Typ   CUCO                               09/18/2001 10:02:34       18432 
    Typ   CUCO_OBJ                           09/18/2001 10:02:34       18432 
    Prg   SAPLCLCA                           09/06/2005 23:33:29       68608 
    Typ   TCLA                               03/13/2004 14:10:20        5120 
    Typ   TCLAO                              08/13/1997 13:57:22        4096 
    Prg   SAPLCUOB                           05/23/2005 14:31:35       31744 
    Typ   INOB                               09/03/1997 03:20:02        4096 
    Prg   SAPLCLSE                           05/23/2005 14:32:26      167936 
    Prg   %_CCC01                            05/01/2005 00:34:57       53248 
    Typ   TABLEKEY                           07/06/1998 21:01:06        2048 
    Typ   KSSK                               09/18/2001 10:02:58        3072 
    Prg   SAPLCLEF                  

  • 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.

  • QM UD Error Message: Check table XEKBN: entry 45039875220001003 does not exist.

    Hello QM expert,
    I encounter a error when I make a UD. (Please refer to below screenshot. )
    Case 1: I did quantity post to unrestricted use, to scrap, to blocked stock, to new material, to reserves, return delivery. When I save this UD, there is a error message 'Check table XEKBN: entry 4503987522000100310100 does not exist.'  (PS. 4503987522 is PO number, but I don't know what it is about 10031010.)
    Case 2: I fill the same field like Case 1, but exclude to new material. It can be passed, no error message.
    Case 3: I only fill one field [to new material. It can be passed, no error message.
    Could you please give me some guidance? Thank you so much.
    Best Regards,
    Fanchao Bu

    Hi Fanchao,
    Form the inspection lot number range, I believe you are using GR form Purchase Order, right? Please confirm the below points -
    1. Is this a normal PO or Sub-contractor's PO?  Please confirm if this issue is happening for every stock posting like Unrestricted, Scrap, Blocked...? or just for one? Can you try one by one for example, move stock form QI => Unrestricted stock only (and do not combine all types together like the attached screenshot) and suggest if that is working.
    2. If this is a non-valuated material you have used (NLAG) for testing? Are you trying to post materials for previous period? Storage Location SM10 is valid?
    If still this issue exist, then potentially, there is some issue with valuation variant linked to valuation area, which is normally maintained in Configuration OPK9. Paralelly, you can request your ABAP team to check FM MB_UPDATE_VALUE_ENQUEUE_TABLE, Include LMBGBU04, as suggested by the below link -
    SAP ABAP Function Module MB_UPDATE_VALUE_ENQUEUE_TABLE - SAP Datasheet - The Best Run SAP Run SAPDatasheet
    You can also check SAP notes below, based on the business needs:
    1. 403671  - Error M7001: 'Please check table &...'
        401462  - Error M7001: 'Please check table &...'
        201833  - M7001: 'Please check table XEKPO: Entry & &...' 
        2072019  - Error M7001 raised during posting goods receipt
        407265  - Transfer parameter with BAPI BAPI_GOODSMVT_CANCEL (this may be linked to your return Delivery of 1 PC...)
        439945  - GR w/ freight costs for stock transport ordr w/ML currencies
        521090  - FAQ: Stock transfer to stock transport order
        867878  - Inconsistencies in the EKBE table because of conversions
        214814  - M7001/M7361: Table T156M, entry MAA7 2
        1584493  - Overdelivery check for GR blocked stock with GR-based IV
        102863  - GI f.delivery f.a stock transfer w.delivery costs
    2. 409529  - Price differences during goods receipt for purchase order
    3. 1528009  - MAA: incorrect distribution of goods receipt quantities
    4. 1569831  - MAA2: Composite SAP Note after Support Package SAPKH60504
    5. 406973  - M7001: Please check table XEBEFU: Entry does not exist
    6. 70577  - QA11: Error M7001 when posting qty in usage decision (OLD NOTE, May not be applicable)
    7. 824322  - QAC1: Incorrect batch in material document (Old Note, may no be applicable)
    Else, you can speak to MM team and/or FI team to help you better in this case, as I feel there is no much QM issues involved.
    Thanks,
    Arijit

  • Access ABAP Table using Java (NWDS/JCO)

    All,
    I am trying to setup a jco connection from java program through NWDS to ECC abap table.
    However I am getting the following error in NWDS:
    Exception in thread "main" java.lang.ExceptionInInitializerError: JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
    JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [C:\Program Files\Java\jdk1.6.0_45\bin\sapjcorfc.dll: Access is denied]. java.library.path [C:\Program Files\Java\jdk1.6.0_45\bin;.]
    and a parity error on my system:
    "Parity blocked an attempt by javaw.exe to run sapjcorfc.dll because the file is not approved.  If you require access to this file, please contact your system administrator.  Scroll down for diagnostic data."
    Here is the Java code...per the SAP website:
    package com.sap.pi.updateAbapSxmbAdminParams;
    import com.sap.mw.jco.*;
    public class ReadPiAbapTables {
      private static JCO.Client theConnection;
      private static IRepository theRepository;
      public static void main(String[] args) {
       createConnection();
       retrieveRepository(); 
       try {
        JCO.Function function = getFunction("RFC_READ_TABLE");
        JCO.ParameterList listParams = function.getImportParameterList();
        listParams.setValue("BSAUTHORS", "QUERY_TABLE");
        theConnection.execute(function);
        JCO.Table tableList = function.getTableParameterList().getTable("SXMSCONFVLV");
        if (tableList.getNumRows() > 0) {
         do {
          for (JCO.FieldIterator fI = tableList.fields();
          fI.hasMoreElements();)
           JCO.Field tabField = fI.nextField();
           System.out.println(tabField.getName()
             + ":t" +
             tabField.getString());
          System.out.println("n");
         while (tableList.nextRow() == true);
       catch (Exception ex) {
        ex.printStackTrace();
      private static void createConnection() {
       try {
        theConnection = JCO.createClient("aaa", "aaa", "aaa", "aa", "aa", "aa");
        theConnection.connect();
       catch (Exception ex) {
        System.out.println("Failed to connect to SAP system");
      private static void retrieveRepository() {
       try {
        theRepository = new JCO.Repository("saprep", theConnection);
       catch (Exception ex)
        System.out.println("failed to retrieve repository");
      public static JCO.Function getFunction(String name) {
       try {
        return theRepository.getFunctionTemplate(name.toUpperCase()).getFunction();
       catch (Exception ex) {
        ex.printStackTrace();
       return null;

    Hi Vicky,
    You need authorization to the S_TABU_DIS object, talk with the ABAP basis team about this to find the more restrictive role.
    It's not a good idea to use the RFC_READ_TABLE, for the wide permissions needed. You could think to develop a Z RFC for this.  You can check pros/cons in this document: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a83ec690-0201-0010-14ac-bd1d75e24a7d?overridelayout=t…
    Regards.

  • XI / PI Alert Framework to Populate an ABAP table

    We are sending an outbound proxy to PI, and if an error occurs in PI, we want to populate an abap table in the source system.  SAP has told us this could only be done via the PI alert framework.  Could someone tell me if there is one or many user exits (and what they are) in the PI alert framework that abap code could be inserted in?

    BAPI- Implementation of interface IF_EX_ALERT_MODIFY_TEXT.

  • How to avoid time out error in abap program

    How to avoid time out error in abap program
    based on performance wise i want please help

    Timeout occurs when a statement exceeds its time limit.To avoid this we need to tune the statements.
    I can give give you few tips for tune a select stament.
    1.The order of the feilds in the select statement should be same as the order of fields in the database table.
    2.It is always advisible to use the key fields when you are using the where clause.
    3. Sort the internal table while using the for all entreis statements.
    4.Use index in where clause if necessary.
    5.When you have a read statement user binary search but before this a sort statement should be there.
    6. Check your program with the Tcode ST05 and check which statement takes much time based on that tune that.

  • Error in the table parameter.

    Hi All,
    I have some Error in a table parameter in the tree model when i created the Dialog program.
    "Errors : ITEM_TABLE contains two items with the same name"
    Please help me to solve this error
    Regards,
    Luke

    Hi,
    As per Data given
    the item_table you created must be having the same field name twice
    (1) eg: imagine if you declared
    item_table type table of ZXXXX
    Check in se11,in the column "Fields" if any field is repeated but if you check syntax,then errror message will be displayed
    or data base inconsistency in activation will come
    (2) if you have declared it as
    data : begin of XXXX
    then you must have repeated a field name by mistake like
    data : begin of XXXX
             field1 type aXXX
             field1 type aXXXX
            end of XXXX
    or in the abap editor double click on item_table , it will take you to its declaration,just check the 2 cases mentioned above
    Pls check and revert
    Regards
    Byju

  • How to check syntax errors in ABAP Queries

    HI Guys,
    How to check syntax errors in ABAP queries, Can please provide the T-Codes.
    Advande thanks to everybody.
    Thanks,
    Gourisankar

    Hi
    with these you can check syntax errors and performance points
    Hi
    these all are doing t he same thing that is checking the program for better performance
    Tools for Performance Analysis
    Run time analysis transaction SE30
    SQL Trace transaction ST05
    Extended Program Check (SLIN)
    Code Inspector ( SCI)
    Run time analysis transaction SE30 :This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.
    SQL Trace transaction ST05: The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
    The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on a particular database table of the ABAP program would be mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
    The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
    To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
    Extended Program Check
    This can be called in through transaction SE38 or through transaction SLIN. This indicates possible problems that may cause performance problems.
    Code Inspector (SCI)
    You can call the Code Inspector from the ABAP Editor (SE38), the Function Builder (SE37), the Class Builder (SE24), or as a separate transaction (SCI).
    The Code Inspector indicates possible problems. However, note that, especially with performance issues: There is no rule without exception. If a program passes an inspection, it does not necessarily mean that this program will have no performance problems.
    reward if usefull

  • Error message "ABAP/4 error during dynamic assign" on Contact Log creation.

    Hi,
    We are getting an error message "ABAP/4 error during dynamic assign beyond program bounds" displayed while creating contact log using transaction "BCT0".
    Please suggest what can be the cause of the error message and how we can remove this.
    Regards,
    Ankur

    Dear Andrea,
    The problem should be caused by obsolete entry in table TFAWX.
    Please use the following report for deleting this entry (test before in your TEST System) :
    report ztfawx_delete.
    tables tfawx.
    select single * from tfawx where prog = 'SAPLBAS0'
                                and bldgr = '0110'
                                and mnum  = 23
                                and bfeld = '$GENERAL'.
    if sy-subrc = 0.
      delete tfawx.
    endif.
    Buona Giornata
    Mauro

  • Plaining function repost button can be update in normal abap table

    Dear ALL,
      There is a standard program for planing function that can repost any number of characteristic in cube by means of repost button in wad. at the same time that particular record has to update in some normal abap tables.Please help me. 
    Regards,
    varun

    Hi,
    What are the infoObject properties for Product color? Is it of type CHAR with length 60?
    Have you de-activated the property 'With master data' in InfoObject maintenance screen for this InfoObject? If not then system will not allow you to enter any free text.
    If you have already done the above settings then you should be able to enter the free text through planning sequence input-template step.
    What error are you getting exactly?
    Regards,
    Deepti

  • System Error During Insert (Table KNMT SUBRC 4)

    Hi All,
    I am getting a peculiar error when i try to update KNMT table using the FM RV_CUSTOMER_MATERIAL_UPDATE.
    When i run it directly in debug mode, entries are getting created perfectly.
    But when i run it through RFC, before the FM is executed itself, during validation, i am getting an error in the message queue stating "System Error During Insert (Table KNMT SUBRC 4).
    I cheked that KNMT table is empty. Also i had deleted all entries using the standard transaction VD52.
    I found that there is a certain FM RV_CUSTOMER_MATERIAL_UPDATE_C which is described as Posting program for customer-material info (CALL mode).
    But i am not sure what this does. I cannot view the documentation in my system and also this FM does not have any parameters.
    Kindly let me know if anyone has encountered an error like this... Please let me know of any suggestions for resolution.
    Thanks & Regards,
    Mz
    P.S : The Functionality seems to work intermittently... though not when i want it.
    Edited by: Mazin Mahmood on Dec 8, 2011 9:09 AM

    Hi,
    The issue was that i was calling the function module RV_CUSTOMER_MATERIAL_UPDATE using an RFC.(ABAP Proxy) For some reason, while using an RFC, there is some issue with this function module and the database commit .
    I had to recode using BDC (for transaction vd51) approach for creating a record in KNMT.
    Thanks All,
    Cheers,
    Mz

  • Error ,message into table

    Hi all,
    i am trying to put a error message into a table...any idea how i can get this without doing move 'matnr & is in error' into my table?
    thanx

    Hi,
    There's a few ways you could do this;
    Construct your message first (i.e. combine the message text and variables into one string, then move this into the table)
    or
    Don't store the text, instead store the message ID, number and variable parts of the message.  This has the advantage if you're running a multi-language system the log can be used by users of different languages.
    Regards,
    Nick

Maybe you are looking for

  • Os 5.1 deleted ALL calendar entries

    Hello all, iPad One. I've just updated to OS 5.1 and when I did a calendar entry all my previous entries disappeared! I thought this only happened in Windows!! This is NOT supposed to happen with an Apple product, or are we going the way of Windows?

  • Dimension size docment size resolution

    Use the picture on website. Really no idea with Resolution, Document Size, Dimension Size and Fit Image Function. Use on Website, don't need to care the Document Size, right? Changing with Resolution Size and Resolution, some time, the Resolution is

  • Risk with Locking and changinf password for SAPCPIC

    Hi All,   Please advice if there is any risk with locking and changing password for SAP standard user SAPCPIC .We are on system 4.6D .   Somewhere I could find that if there is any RFC destination defined with this user then it may cause problem afte

  • Need info about classpath

    Hi just give me any tutorial links or any explanations regarding classpath's character thanks

  • Where is Adobe Extension Manager CS5 5.0?

    My computer tells me Adobe Extension Manager CS5 5.0 is an update I should load.   I can't find it anywhere on Adobe's downloads for photoshop web site.   Where do I find it?    I'm using windows 8.1. David