Snap_no_new_entry ABAP dump coming while ST22 is reorganized regularily

Dear Friends,
snap_no_new_entry ABAP dump comes and hamper all activities while ST22 is reorganized daily. After restarting the server, It is working fine for a day only. Can you suggest in this regard to fix this problem permanently?
System Environment : SAP ECC 6.0, AIX, DB2
Table spaces :
Tablespace
  Name
TS Type
KB Total
Percent Used
KB Free
Page Size (KB)
High-Water Mark
  (KB)
No. Containers
Contents
TS State
AUTORESIZE
PSAPTEMP16
SMS
64
100.00
0
16
0
4
Temporary objects
Normal
NO
SYSTOOLSTMPSPACE
SMS
64
100.00
0
16
0
4
Temporary objects
Normal
NO
ECP#BTABD
DMS
6422528
99.94
3680
16
6418720
4
Large objects
Normal
YES
ECP#ES702DX
DMS
35586048
99.94
21888
16
35564032
4
Large objects
Normal
YES
ECP#EL702DX
DMS
18972672
99.93
13632
16
18958912
4
Large objects
Normal
YES
SYSCATSPACE
DMS
2785280
99.67
9216
16
2775936
4
Regular data
Normal
YES
ECP#ES702IX
DMS
7471104
99.58
31456
16
7439520
4
Large objects
Normal
YES
ECP#STABD
DMS
3637248
99.58
15424
16
3621696
4
Large objects
Normal
YES
ECP#POOLD
DMS
6258688
99.54
28832
16
6252608
4
Large objects
Normal
YES
ECP#POOLI
DMS
3637248
99.47
19200
16
3617920
4
Large objects
Normal
YES
SAPTOOLS
DMS
3053056
99.14
25120
16
3027808
4
Large objects
Normal
YES
ECP#PROTD
DMS
851968
98.94
9056
16
842784
4
Large objects
Normal
YES
ECP#BTABI
DMS
2457600
98.81
29344
16
2428128
4
Large objects
Normal
YES
ECP#CLUD
DMS
491520
98.75
6144
16
485248
4
Large objects
Normal
YES
ECP#STABI
DMS
2424832
96.81
77280
16
2400160
4
Large objects
Normal
YES
ECP#SOURCED
DMS
458752
95.02
22848
16
435776
4
Large objects
Normal
YES
ECP#SOURCEI
DMS
458752
93.34
30528
16
428096
4
Large objects
Normal
YES
SYSTOOLSPACE
DMS
229376
92.70
16736
16
212512
4
Large objects
Normal
YES
ECP#EL702IX
DMS
98304
84.29
15424
16
82752
4
Large objects
Normal
YES
ECP#LOADD
DMS
131072
79.86
26368
16
104576
4
Large objects
Normal
YES
ECP#PROTI
DMS
131072
77.57
29376
16
101568
4
Large objects
Normal
YES
ECP#CLUI
DMS
65536
63.31
24000
16
41408
4
Large objects
Normal
YES
ECP#DDICI
DMS
1015808
63.13
374464
16
986816
4
Large objects
Normal
YES
ECP#DDICD
DMS
5439488
61.23
2108736
16
5436512
4
Large objects
Normal
YES
ECP#DOCUD
DMS
65536
51.91
31456
16
53024
4
Large objects
Normal
YES
ECP#LOADI
DMS
32768
48.53
16800
16
15840
4
Large objects
Normal
YES
ECP#DOCUI
DMS
65536
36.25
41696
16
35744
4
Large objects
Normal
YES
ECP#USER1D
DMS
32768
30.69
22624
16
10016
4
Large objects
Normal
YES
ECP#USER1I
DMS
32768
30.00
22848
16
9792
4
Large objects
Normal
YES
SAPEVENTMON
DMS
51200
28.38
36576
16
14496
4
Large objects
Normal
YES
ECP#DIMD
DMS
32768
25.29
24384
16
8256
4
Large objects
Normal
YES
ECP#DIMI
DMS
32768
25.29
24384
16
8256
4
Large objects
Normal
YES
ECP#EL702I
DMS
32768
25.29
24384
16
8256
4
Large objects
Normal
YES
ECP#FACTD
DMS
32768
25.29
24384
16
8256
4
Large objects
Normal
YES
ECP#FACTI
DMS
32768
25.29
24384
16
8256
4
Large objects
Normal
YES
ECP#ODSD
DMS
32768
25.29
24384
16
8256
4
Large objects
Normal
YES
ECP#ODSI
DMS
32768
25.29
24384
16
8256
4
Large objects
Normal
YES
ECP#ES702I
DMS
6651904
0.12
6643520
16
8256
4
Large objects
Normal
YES
ECP#EL702D
DMS
17334272
0.05
17325888
16
8256
4
Large objects
Normal
YES
ECP#ES702D
DMS
31391744
0.03
31383360
16
8256
4
Large objects
Normal
YES

Hi Dharmendra,
The error implies SNAP table is full in the SAP system and it cannot write new entries. Since you tried to perform reorganize using ST22 , I would request you to do the following
1) Check whether Transaction log is full. If yes, then either take backup of transaction log or shrink the same, you can check db2diag.log for more details.
Note : As per log if any process making the log to fill , kindly terminate it
2) Restart SAP and database.
3) Repeat the ST22 dump Re-organization process.
Hope it helps
BR Vaibhav

Similar Messages

  • 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

  • Abap dump error while release Production order

    Dear Gurus,
                          Abap dump error is creating while release production order , pour some light on this issue.
    Regards,
    Kamal

    Hello,
      use transaction ST22 to analyze the error type. There you have the detail of the error message, the program and the line of the ABAP code where the dump was triggered.
    Best regards,
    Andrea

  • ABAP Dump issue while accessing Gateway

    Hi
    We have recently upgraded our Gateway server to SP03. Eversince after service generation while accessing the XML/Metadata from the consumption page we get an HTTP error with Dump. Has anyone faced this problem before.
      <?xml version="1.0" encoding="utf-8" ?>
    - <error xmlns:xsi="http://www.w3.org/2001/XMLSchema-Instance">
      <code>HTTP/500/E/Internal Server Error</code>
      <message>Call of service /sap/opu/sdata/sap/Z14335_RFC_BP_1/ terminated because of an error. The following error text was processed in system AC1 : Syntax error in program /IWCOR/CL_REST_HTTP_HANDLER===CP .The error occurred on the application server njsapnet3. The termination type was: RABAX_STATE.If the termination type is RABAX_STATE, you will find more information on the cause of termination in system AC1 in transaction ST22. If the termination type is ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server njsapnet3 in transaction SM21. If the termination type is ERROR_MESSAGE_STATE, you can search for further information in the trace file for the work process in transaction ST11 on the application server njsapnet3. You may also need to analyze the trace files of other work processes. If you do not yet have a user ID, contact your system adminmistrator.</message>
      </error>

    Hi All,
    I am also facing the same issue.
    When i am executing query/read operation my service it will works properly and getting data also,but when i am trying get X-CSRF token it throws error(ABAP Dump) .Can you please help me out this issue.
    Based on the Tx: ST11..getting below log.
    A  ABAP Program /IWCOR/CL_REST_HTTP_HANDLER===CP        .
    A  Source /IWCOR/CL_REST_HTTP_HANDLER===CCIMP      Line 40.
    A  Error Code ASSERTION_FAILED.
    A  Module abassert.c.
    A  Function ab_aabAssertionFailedRabax Line 1880.
    A  ** RABAX: level LEV_RX_STDERR completed.
    A  ** RABAX: level LEV_RX_RFC_ERROR entered.
    A  ** RABAX: level LEV_RX_RFC_ERROR completed.
    A  ** RABAX: level LEV_RX_RFC_CLOSE entered.
    A  ** RABAX: level LEV_RX_RFC_CLOSE completed.
    A  ** RABAX: level LEV_RX_IMC_ERROR entered.
    A  ** RABAX: level LEV_RX_IMC_ERROR completed.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.
    A  ** RABAX: level LEV_RX_ERROR_SAVE entered.
    A  ** RABAX: level LEV_RX_ERROR_SAVE completed.
    A  ** RABAX: level LEV_RX_ERROR_TPDA entered.
    A  ** RABAX: level LEV_RX_ERROR_TPDA completed.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    A  ** RABAX: level LEV_RX_END entered.
    A  ** RABAX: level LEV_RX_END completed.
    N
    N Thu Jan 03 15:00:58 2013
    N  *** ERROR => System ID and client from ticket are not the same than mine. [ssoxxkrn.c   1065]
    N  {root-id=0050569E07B31ED295B108EAC1527575}_{conn-id=0050569E07B31ED295B108EABC707575}_1
    N  *** ERROR => Neither was ticket issued by myself nor can I find issuer in TWPSSO2ACL (see note 1055856). [ssoxxkrn.c   1071]
    N  {root-id=0050569E07B31ED295B108EAC1527575}_{conn-id=0050569E07B31ED295B108EABC707575}_1
    i am getting based on Tx:ST22
    Category          
    ABAP Programming Error
    Runtime Errors    
    ASSERTION_FAILED
    ABAP Program      
    /IWCOR/CL_REST_HTTP_HANDLER===CP
    Application Component  OPU-FND-CCL
    Note: I am using SAP NW-GW-SP04
    Thanks,
    Syam

  • ABAP dump coming at the time of displaying error message.

    Hi to all
    I have written a code in user exit .
    At the time of saving ABAP dump is coming instead of showing error message.
    Error analysis
        The program attempted to issue a " " message during "Exit Command" processing.
    This is an illegal operation. The program was terminated.
    Screen name.............. "SAPMV45A"
    Screen number............ 4008
    My coding :
    >>>>>     IF vbak-vkbur IS NOT INITIAL.
       70       IF wa-vkbur NE vbak-vkbur.
       71         MESSAGE E000(yi01) WITH 'SALES OFFICE Mismatch Please Check for Customer-'vbak-kunnr
       72       ENDIF.
       73     ENDIF.
    Please guide to resolve the issue.
    This application is working fine for sales order creation.
    Regards
    Anubhav

    Hi
    Instead of error message, try using the following code.
    MESSAGE <your message> TYPE 'I' DISPLAY LIKE 'E'.
    Thanks
    Sourav

  • RFC_NO_AUTHORITY ABAP dumps coming very frequently

    Hello
    We are getting abap dumps in Production system and the details are below :
    RFC_NO_AUTHORITY
    ABAP dumps RFC_NO_AUTHORITY are coming very frequently in the Production system. The dumps are occurring for user ID "SOLM_REMOTE" in DBCI only. This dumps comes every hour from Sep to till date. Also in the short text it has mentioned, User "User "SOLM_REMOTE" has no RFC authorization for function group "TMW_TRACKING". The termination occurred in the ABAP/4 program "SAPLTMW_TRACKING " in "TMW_VERSION_TEST". The main program was "SAPMSSY1 ".
    Provided the RFC authorization for function group "TMW_TRACKING" for the user SOLM_REMOTE.
    The user SOLM_REMOTE has all the authorizations.From the authorization perspective everything seems to be fine.
    But still we are getting many RFC_NO_AUTHORITY abap dumps frequently in production system.
    Please help me in this regard.
    Many thanks in Advance.
    Regards
    Sreedhar Reddy.

    Hai,
    Please check the below link, it might help you.
    http://help.sap.com/saphelp_nw04/helpdata/en/4f/b541d812aea34695d54758cec0796f/frameset.htm
    Regards,
    Yoganand.V

  • ABAP dump error while updating product master in APO

    Hi All,
    Greetings from Vijay!
    I need to your help to resolve below issue ;
    I am getting error '
    No simulation parameters could be set for the
    active version'
    While i am updating and trying to assign active version to my product master in APO which are created in APO for regression testing
    and also sometimes system throwing dump error'
    Error in the ABAP Application Program
    The current ABAP program "/SAPAPO/SAPLDM_LC_SQL" had to be terminated because
      it has
    come across a statement that unfortunately cannot be executed.;
    I appreciate your help
    Thanks
    Vijay Job

    Hi Vijay,
    Can you check note 1465462 ?
    The same problem is mentioned in the note with correction .
    Regards,
    Mukesh pandey

  • ABAP dump(SAPSQL_ARRAY_INSERT_DUPREC) while creating a delivery

    Hello Friends,
    I am getting the dump while creating the delivery .The error details are as follows.
    The ABAP/4 Open SQL array insert results in duplicate database record
    What happened?
    The current ABAP/4 program "SAPLV05I " had to be terminated because
    one of the statements could not be executed.
    How to correct the error
    Use an ABAP/4 Open SQL array insert only if you are sure that none of
    the records passed already exists in the database.
    If the error occurred in a non-modified SAP program, you may be
    able to find a solution in the SAP note system.
    If you have access to the note system yourself, use the following
    search criteria:
    "SAPSQL_ARRAY_INSERT_DUPREC"
    "SAPLV05I " or "LV05IU15 "
    "SD_PARTNER_UPDATE"
    Source code extract
    004500                                           POSNR = I_XVBPA-POSNR
    004510                                           PARVW = I_XVBPA-PARVW.
    004520               IF I_YVBPA-STCD1 <> I_XVBPA-STCD1 OR
    004530                   I_YVBPA-STCD2 <> I_XVBPA-STCD2 OR
    004540                   I_YVBPA-STCD3 <> I_XVBPA-STCD3 OR
    004550                   I_YVBPA-STCD4 <> I_XVBPA-STCD4 OR
    004560                   I_YVBPA-STCDT <> I_XVBPA-STCDT OR
    004570                   I_YVBPA-STKZN <> I_XVBPA-STKZN OR
    004580                   I_YVBPA-J_1KFREPRE <> I_XVBPA-J_1KFREPRE OR
    004590                   I_YVBPA-J_1KFTBUS <> I_XVBPA-J_1KFTBUS OR
    004600                   I_YVBPA-J_1KFTIND <> I_XVBPA-J_1KFTIND.
    004610                 MOVE-CORRESPONDING I_XVBPA TO WA_XVBPA3I.
    004620                 APPEND WA_XVBPA3I TO DA_XVBPA3I.
    004630               ENDIF.
    004640             ENDIF.
    004650           ENDIF.
    004660         WHEN UPDKZ_OLD.
    004670           IF DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_OLD   OR
    004680              DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_ADRC.
    004690             YADR-ADRNR = DA_VBPA-ADRNR. COLLECT YADR.
    004700           ENDIF.
    004710           IF DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_OLD   OR
    004720              DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_ADRC.
    004730             XADR-ADRNR = DA_VBPA-ADRNR. COLLECT XADR.
    004740           ENDIF.
    004750       ENDCASE.
    004760     ENDLOOP.
    004770     UPDATE (OBJECT) FROM TABLE DA_XVBPAU.
    004780     UPDATE VBPA3 FROM TABLE DA_XVBPA3U.
    004790
         >     INSERT (OBJECT) FROM TABLE DA_XVBPAI.
    004810     INSERT VBPA3 FROM TABLE DA_XVBPA3I.
    004820
    004830     IF SY-SUBRC > 0.
    Could you please suggest me ,what could be the reason for dump and how to avoid dump?
    <REMOVED BY MODERATOR>
    Thank you in advance,
    Arvind.
    Edited by: Alvaro Tejada Galindo on Apr 22, 2008 5:16 PM
    Edited by: Alvaro Tejada Galindo on Apr 22, 2008 5:16 PM

    Hello, I have very same error
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Exception              CX_SY_OPEN_SQL_DB
    Transaction......... "VL01N "                                                                
    Program............. "SAPLV05I"                                                              
    Screen.............. "RSM13000 3000"                                                         
    Screen line......... 2   
    SAP kernel....... 700  
    Patch level. 75 
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"                             
    SAP database version. 700                                                                    
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2" 
    The ABAP/4 Open SQL array insert results in duplicate database records.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught  in procedure "SD_PARTNER_UPDATE" "(FUNCTION)", nor was it propagated by a RAISING clause.
    I use SAP_APPL SAPKH60006 Support Package
    The NUMBER RANGE OBJECT HAS NO ERRORS!
    I went trough the zillions of notes all of them affect the old releases.... Please advice.
    Patiently yours,
    SAP User

  • ABAP DUMP:MEMORY LOW

    Dear all,
    While running a particular report ZMIS in my production server I am getting the following error.Well I also found this is coming for other reports also where we have to fetch data for 3-4 months.This is the dump I am getting
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
    In the system profile, set the parameters
    -abap/heap_area_dia and
    -abap/heap_area_nondia
    to a maximum of 1089891456. To be on the safe side, reduce the value by 10,000,
    000.
    Then restart the SAP system.
    I had added abap/heap_area_dia and
    -abap/heap_area_nondia profiles and set them to 2GB. Also I had increased my abap/buffersize from 300MB to 400MB and restarted the server,still dump is coming.
    I have even reported the error to SAP as asked by our implementation partner. SAP asked us to send the memory parameter. I asked SAP to please specify the name of the memory parameter and still waiting for their reply. If you know what memory parameter they are asking me to send it would be a great help.I checked in RZ11 and there are aroung 500 parameter and I guess they want me send the default values of these parameters.
    Please suggest..
    Regards,
    vicky
    Edited by: vicky singh on Jun 16, 2008 7:57 AM
    Edited by: vicky singh on Jun 16, 2008 7:59 AM

    Dear Rahul,
    Thnx for your reply.SAP said:
    The issue here is not parameters as such, it is the fact that you run
    your SAP system on a 32bit CPU and this is the result of a lack of
    address space for the process because of the 32bit CPU you have, there are some things that you can possibly do to help.
    Do you know what are address space and how to increase it..?
    Our server are installed on 32bit CPU. Do I need to install my server on 64bit CPU or some alternative solution exists..?
    Obviously I am waiting for SAP reply before doing anything and reinstalling server now is not possible.
    Please share some views..
    Regards,
    Vicky

  • ABAP runtime error while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N

    Dear All Expert,
    I am facing problem while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N,
    Please find the below ABAP Runtime Error.
    Runtime Errors         LOAD_TYPE_VERSION_MISMATCH
    Date and Time          10.02.2011 11:13:07
    Short text
         Change of a Dictionary structure at runtime of a program.
    What happened?
         Runtime error
         The current ABAP program "CL_IM_WRF_MM_PROC_PO==========CP" had to be
          terminated because one
         of the statements could not be executed at runtime.
    What can you do?
         Restart the program.
         If the error persists, contact your SAP administrator.
         You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
    Error analysis
         The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY"
          changed
         during the flow of the transaction.
         As the type was already used in the old version
         and in the new type should be used in the same transaction in the new
          version, the transaction had to be cancelled to avoid inconsistencies.
    How to correct the error
        Try to restart the program.
    System environment
        SAP-Release 700
        Application server... "iqe"
        Network address...... "172.25.0.85"
        Operating system..... "Linux"
        Release.............. "2.6.9-55.ELsmp"
        Hardware type........ "x86_64"
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 0
        Shortdump setting.... "full"
        Database server... "iqe"
        Database type..... "ORACLE"
        Database name..... "IQE"
        Database user ID.. "SAPSR3"
        Terminal................. "MUMJML5727"
        Char.set.... "C"
        SAP kernel....... 700
        created (date)... "Dec 26 2010 20:17:07"
        create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
        Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 285
    Patch text.. " "
    Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
    SAP database version. 700
    Operating system..... "Linux 2.6"
    Memory consumption
    Roll.... 16192
    EM...... 25139088
    Heap.... 0
    Page.... 40960
    MM Used. 8038136
    MM Free. 4528408
    User and Transaction
    Client.............. 600
    User................ "JKMM"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "4D524AD1FD7A42F9E1000000AC190055"
    Program............. "CL_IM_WRF_MM_PROC_PO==========CP"
    Screen.............. " "
    Screen line......... " "
    Information on where terminated
        The termination occurred during generation of the ABAP/4 program
         "CL_IM_WRF_MM_PROC_PO==========CP".
        The termination occurred in line 213
        of the source code of program "CL_IM_WRF_MM_PROC_PO==========CM007" (when
         calling the editor 2130).
    Source Code Extract
    Line  SourceCde
      183   DATA: l_flag TYPE wrf_pbas_boolean.
      184
      185   CALL FUNCTION 'WRF_POHF_MSG_READ_PREVIEW_FLAG'
      186     IMPORTING
      187       e_preview_flag = l_flag.
      188
      189   IF NOT l_flag IS INITIAL.
      190
      191     DATA: l_header TYPE REF TO cl_po_header_handle_mm.
      192
      193     MOVE im_header ?TO l_header.
      194
      195     CALL METHOD l_header->if_output_mm~preview( ).
      196
      197     CALL FUNCTION 'WRF_POHF_MSG_RESET_PREV_FLAG'.
      198
      199 ***$ Widening Cast for printing information.
      200 **    CALL FUNCTION 'WRF_POHF_STORE_PRINT_INFO_SET'
      201 **      EXPORTING
      202 **        im_header = l_header.
      203
      204 * Printing Preview
      205 * IF NOT gv_preview IS INITIAL.
      206 *    CALL METHOD l_header->if_output_mm~overview( ).
      207 *    CALL METHOD l_header->if_output_mm~preview( ).
      208 * clear gv_preview.
      209   ENDIF.
      210
      211 *  ENDIF.
      212
    >>>>> ENDMETHOD.
    Internal notes
        The termination was triggered in function "ab_RxDdicStruShareFailed"
        of the SAP kernel, in line 2539 of the module
         "//bas/700_REL/src/krn/runt/abtypload.c#11".
        The internal operation just processed is " ".
        Internal mode was started at 20110210111306.
        Name of the changed type......: "WRF_POHF_KOMP_STY"
        New version of the type.......: 20070508193207
        Old version of the type.......: 20070508193207
        New user......................: "Type" "WRF_POHF_KOMP_STY"
        Version of the new user.......: 20070508193207
        Old user......................: "???" "???"
        Version of the old user.......: "???"
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    (CTrcStack2+0x78)[0x6cbb78]
    (CTrcStack+0xb)[0x6cc17b]
    (ab_rabax+0x3be5)[0xb8d985]
    (_Z24ab_RxDdicStruShareFailedPKtm4RUDIS0_S1_S0_+0x163)[0xb16823]
    (_Z19ab_GetDdicTypeIndexPKtm4RUDI+0x1f6)[0xb0dbb6]
    (_Z11ab_LoadViewPtjPKtPK11PROGRAMHEADPj+0x27e)[0xb16ede]
    (_Z18ab_GetDdicTypeLoad4RUDI+0x6e)[0xb1705e]
    (ab_GetView+0xc1d)[0xb0ee1d]
    (_Z20CompressInitRcByDatajPK6CG_DIRjjS1_jj4RUDIPKhj+0x60d)[0xe32b2d]
    (_Z21cg_CompressStackFrameP4TRIGjj+0x169)[0xe33399]
    (_Z8cg_blkleP3ENV+0x75f)[0xe4779f]
    (_Z9sc_cblklePKt8ENV_KINDP7SC_INFO+0x394)[0xe90024]
    (sc_blkle+0xdd)[0xec6e4d]
    (rs_oper_abap1729+0x37)[0x10eb237]
    (rs_expan_abap+0xa1996)[0xfd7a2a]
    (_Z8sc_expanj+0x76d)[0xe1d55d]
    (_Z5parsejPi+0x258)[0xe19998]
    (sc_check+0xb9c)[0xe1857c]
    (sc_inclu+0x5fa)[0xe0d50a]
    (rs_oper_abap2160+0x3a)[0x1115d6a]
    (rs_expan_abap+0xcd41d)[0x10034b1]
    (_Z8sc_expanj+0x76d)[0xe1d55d]
    (_Z5parsejPi+0x258)[0xe19998]
    (sc_check+0xb9c)[0xe1857c]
    (sc_checkStart+0x41)[0xe1ac51]
    (cg_generate+0xb65)[0xe57755]
    (ab_gabap+0x14a)[0xb01a5a]
    (dy_gen_abap+0x63c)[0x74428c]
    (ab_genprog+0x13d3)[0xb03d13]
    (_Z17ab_LoadProgOrTrfoPKtjPj+0xb56)[0x8f9ab6]
    (_Z11ab_LoadProgPKtj+0x11)[0x8f9ca1]
    (_Z15LoadGlobalClassPKtjjj9ClasState+0x24c)[0x958c2c]
    (_Z11FillCfixIntPK4CREFP4CFIXjj9ClasState+0x214)[0x957404]
    (_Z11ab_FillCfixtj+0x65)[0x957ae5]
    (_Z26ab_CrefToCladId_ActivateOKtPh+0x7d)[0x957b6d]
    (_Z8ab_jaboov+0x623)[0x959793]
    (_Z8ab_extriv+0x607)[0x8ba9c7]
    (_Z9ab_xeventPKt+0x1c1)[0xa1c021]
    (_Z8ab_triggv+0x9c)[0xa1c77c]
    (ab_run+0x97)[0xbde5c7]
    (N_ab_run+0x9)[0x736359]
    (dynpmcal+0x669)[0x7333b9]
    (dynppai0+0x8eb)[0x734d9b]
    (dynprctl+0x3e9)[0x733db9]
    (dynpen00+0x4a5)[0x726eb5]
    (Thdynpen00+0x359)[0x541bd9]
    (TskhLoop+0xc49)[0x54d999]
    (ThStart+0x20f)[0x55b29f]
    (DpMain+0x2da)[0x4bd49a]
    (nlsui_main+0x9)[0x4910c9]
    (main+0x33)[0x491103]
    /lib64/tls/libc.so.6(__libc_start_main+0xdb)[0x3cde51c3fb]
    Please help me to resolve the issue.
    Thanks & Regards
    SKK

    read this part again:  The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY" changed during the flow of the transaction. As the type was already used in the old version and in the new type should be used in the same transaction in the new version, the transaction had to be cancelled to avoid inconsistencies. How to correct the error Try to restart the program
    how often had you restarted ME21N before you posted this message?
    In best case this message appears only once, because the program / or dictionary was changed while you executed ME21N
    If many times, then contact your ABAPer, because then he probably did not transport all objects that were changed, or the objects have to be regenerated in your system.

  • ABAP DUMP Dynpro_send_in_background occurs in ECC5.0

    Hi experts,
    We have one ECC5.0 environment which runs on AIX5.3 , and since yesterday, we have lots of ABAP dump Dynpro_send_in_background in st22, could anyone help me? I have searched from OSS and SDN, but seems no suitable case I can reference for our system. Please give me some hint,thank you.
    System information
    Version ：ECC5.0
    patch level ：version 6.40 level 125
    Database version ：Oracle 9.2.0.7
    Long text in ST22
    Runtime Error          DYNPRO_SEND_IN_BACKGROUND
    Date and Time          01.07.2008 17:05:09
    ShrtText
        Screen output without connection to user.
    What happened?
        Error in ABAP application program.
        The current ABAP program "SAPMSSY0" 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
        During background processing, the system attempted to send a
        screen to a user.
        Current screen: "SAPMSSY0 " 0120.
    How to correct the error
        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:
        "DYNPRO_SEND_IN_BACKGROUND" C
        "SAPMSSY0" or " "
        "SYSTEM-EXIT"
        If you cannot solve the problem yourself and you wish to send
        an error message to SAP, include the following documents:
        1. A printout of the problem description (short dump)
           To obtain this, select in the current display "System->List->
           Save->Local File (unconverted)".
        2. A suitable printout of the system log
           To obtain this, call the system log through transaction SM21.
           Limit the time interval to 10 minutes before and 5 minutes
           after the short dump. In the display, then select the function
           "System->List->Save->Local File (unconverted)".
        3. If the programs are your own programs or modified SAP programs,
           supply the source code.
           To do this, select the Editor function "Further Utilities->
           Upload/Download->Download".
        4. Details regarding the conditions under which the error occurred
           or which actions and input led to the error.
    System environment
        SAP Release.............. "640"
        Application server....... "yatptcp"
        Network address.......... "10.1.250.65"
        Operating system......... "AIX"
        Release.................. "5.3"
        Hardware type............ "00001E22D700"
        Character length......... 16 Bits
        Pointer length........... 64 Bits
        Work process number...... 4
        Short dump setting....... "full"
        Database server.......... "yatptcp"
        Database type............ "ORACLE"
        Database name............ "TCP"
        Database owner........... "SAPTCP"
        Character set............ "C"
        SAP kernel............... "640"
        Created on............... "May 1 2006 20:49:14"
        Created in............... "AIX 1 5 00538A4A4C00"
        Database version......... "OCI_920 "
        Patch level.............. "125"
        Patch text............... " "
        Supported environment....
        Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
         10.2.0.."
        SAP database version..... "640"
        Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
        Memory usage.............
        Roll..................... 16192
        EM....................... 25139136
        Heap..................... 0
        Page..................... 835584
        MM Used.................. 8185592
        MM Free.................. 191328
        SAP Release.............. "640"
    User and Transaction
        Mandant............. 400
        Benutzer............ "KOERFCUSER"
        Sprachenschlüssel... "E"
        Transaktion......... " "
        Programm............ "SAPMSSY0"
        Dynpro.............. "SAPMSSY0 0120"
        Dynprozeile......... 0
        Informationen zum Aufrufer des Remote Function Calls (RFC):
        System.............. "TCP"
        Datenbank-Release... 640
        Kernel-Release...... 640
        Verbindungstyp...... 3 (2 = R/2, 3 = R/3, E = Extern, R = Reg. Extern)
        Aufrufsart.......... "synchron (imode 1)" (S = Synchron, a/A = Asynchron, T =
         Transakt. )
        Mandant............. 400
        Benutzer............ "KOERFCUSER"
        Transaktion......... " (Program: SAPLEDIN)"
        Funktionsbaustein... "IDOC_START_INBOUND"
        Aufruf-Destination.. "NONE"
        Quell-Server........ "yatptcp_TCP_01"
        Quell-IP-Adresse.... "10.1.250.65"
        Zusatzinformation zum RFC-Logon:
        Trusted Beziehung... " "
        Logon-Returncode.... 0
        Trusted-Returncode.. 0
        Bemerkung: Bei Releases < 4.0 sind die Informationen zum RFC-Aufrufer teilweise nicht vorhanden.
    Information on where terminated
        The termination occurred in the ABAP program "SAPMSSY0" in "SYSTEM-EXIT".
        The main program was "SAPMSSY4 ".
        The termination occurred in line 0 of the source code of the (Include)
         program " "
        of the source code of program " " (when calling the editor 00).
    Active Calls/Events
    No.   Ty.          Program                             Include
          Name
        1 EVENT        SAPMSSY0                            ???
          SYSTEM-EXIT
    Chosen variables
    Name
        Val.
    No.       1 Ty.          EVENT
    Name  SYSTEM-EXIT
    SY-XPROG
        SAPMSSY0
        0000000000000000000000000000000000000000
        0000000000000000000000000000000000000000
        5454555322222222222222222222222222222222
        310D339000000000000000000000000000000000
    SY-XFORM
        NEW-LINE
        000000000000000000000000000000
        000000000000000000000000000000
        445244442222222222222222222222
        E57DC9E50000000000000000000000
    Internal notes
        The termination occurred in the function "dynpex00" of the SAP
        Basis System, specifically in line 1513 of the module
         "//bas/640_REL/src/krn/dynp/dymain.c#9".
        The internal operation just processed is "----".
        The internal session was started at 20080701170507.
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    => 64 bit R/3 Kernel
    => 64 bit AIX Kernel
    => Heap limit      = unlimited
    => Stack limit     = 4294967296
    => Core limit      = 1073741312
    => File size limit = unlimited
    => Heap address  = 0x0x118a5cf20
    => Stack address = 0xfffffffffff9f50
    => Stack low     =  0xfffffffffff9f50
    => Stack high    =  0xffffffffffff890
    => Stack Trace:
    #AixStack() at 0x10004ae04
    #CTrcStack2() at 0x10004aefc
    #rabax_CStackSave__Fv() at 0x10007bb2c
    #ab_rabax() at 0x100078bd8
    #dypex00() at 0x10020a204
    #dynpoutf() at 0x1011990c0
    #dynprctl() at 0x10119fcf8
    #dynpen00() at 0x10020de20
    #Thdynpen00() at 0x1000a51f8
    #TskhLoop() at 0x1000a884c
    #tskhstart() at 0x1000becdc
    #DpMain() at 0x101742da4
    #nlsui_main() at 0x101716148
    #main() at 0x101716104

    Dear All,
    Any Solution for this similar problem -  In Web Dynpro Application when we call the following application the DYNPRO_SEND_IN_BACKGROUND runtime error happens.
    Note
         The following error text was processed in the system XXX : Screen output without connection to user.
         The error occurred on the application server xxxxxxxx_XXX_00 and in the work process 0 .
         The termination type was: RABAX_STATE
         The ABAP call stack was:
    SYSTEM-EXIT of program SAPLSTRD
    Function: TRINT_POPUP_EDIT_CANCEL_SHOW of program SAPLSTRD
    Form: RAISE_ERROR of program SAPLSTRD
    Function: TRINT_OBJECTS_CHECK_AND_INSERT of program SAPLSTRD
    Function: TR_OBJECTS_CHECK of program SAPLSTRD
    Function: RH_HRPOBJECT_CORR_AT_SAVE of program SAPLRHWM
    Form: UPDATE of program SAPUP50R
    Form: PUT_INFOTYP_BUFFER of program SAPFP50P
    Form: %_PROCESS_P_O_C of program SAPMSSY0
    Form: %_COMMIT of program SAPMSSY0
    What can I do?
         If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system E6Q in transaction ST22.
         If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server xxxxxxx_XXX_00 in transaction SM21.
         If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server qltr01d3801_E6Q_00 . In some situations, you may also need to analyze the trace files of other work processes.
         If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 300 -u: X.XXXX -l: E -s: E6Q -i: xxxxxx_XXX_00 -w: 0 -d: 20080709 -t: 155438 -v: RABAX_STATE -e: DYNPRO_SEND_IN_BACKGROUND
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team

  • Regarding EXPORT_COMPRESS_ERROR ABAP dump

    Hello Experts,
    In our BI System, we are getting EXPORT_COMPRESS_ERROR ABAP dump. And not able to find out any SAP notes regarding this dump.
    Waiting for your kind response.
    Runtime Errors         EXPORT_COMPRESS_ERROR
    Date and Time          11.04.2008 16:40:42
    Short text
    Internal error when compressing data.
    What happened?
    Error in the SAP kernel.
    The current ABAP "SAPLRSDRI_SERVICES" program had to be terminated because the
    ABAP processor detected an internal system error.
    In the EXPORT TO DATABASE statement, an internal error occurred
    when compressing data.
    What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
    Error analysis
    There is an internal system error.
    eliminated with ABAP/4.
    Last error logged in SAP kernel
    Component............ "EM"
    Place................ "SAP-Server u962004s_P38_67 on host u962004s (wp 23)"
    Version.............. 37
    Error code........... 7
    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
    Description.......... " "
    System call.......... " "
    Module............... "emxx.c"
    Line................. 1881
    The error reported by the operating system is:
    Error number..... " "
    Error text....... " "
    How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "EXPORT_COMPRESS_ERROR" " "
    "SAPLRSDRI_SERVICES" or "LRSDRI_SERVICESF01"
    "DATA_WRAP_UC"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "u962004s"
    Network address...... "10.200.230.110"
    Operating system..... "HP-UX"
    Release.............. "B.11.23"
    Hardware type........ "ia64"
    Character length.... 8 Bits
    Pointer length....... 64 Bits
    Work process number.. 23
    Shortdump setting.... "full"
    Database server... "u962004s"
    Database type..... "ORACLE"
    Database name..... "P38"
    Database user ID.. "SAPP38"
    Char.set.... "de_DE.iso88591"
    SAP kernel....... 700
    created (date)... "Dec 30 2007 21:06:56"
    create on........ "HP-UX B.11.23 U ia64"
    Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 141
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "HP-UX B.11"
    Memory consumption
    Roll.... 6219104
    EM...... 2291965488
    Heap.... 2302579280
    Page.... 16384
    MM Used. 4399764848
    MM Free. 194652624
    User and Transaction
    Client.............. 100
    User................ "K59461"
    Language Key........ "D"
    Transaction......... " "
    Transactions ID..... "47FF35AD14F65486E10000000AC8E66E"
    Program............. "SAPLRSDRI_SERVICES"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "P38"
    Database Release.... 700
    Kernel Release...... 700
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "asynchron with reply and non-transactional (emode 0,
    imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. 100
    User................ "K59461"
    Transaction......... " "
    Call Program........."SAPLZ_ZOP01_VCUBES"
    Function Module..... "RSDRI_INFOPROV_READ_RFC"
    Call Destination.... "NONE"
    Source Server....... "u962004s_P38_67"
    Source IP Address... "10.200.230.110"
    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0
    Note: For releases < 4.0, information on the RFC caller are often
    only partially available.
    Information on where terminated
    Termination occurred in the ABAP program "SAPLRSDRI_SERVICES" - in
    "DATA_WRAP_UC".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 194
    of the (Include) program "LRSDRI_SERVICESF01".
    Source Code Extract
    Line
    SourceCde
    164
    165
    CLEAR: l_string.
    166
    167
    CALL METHOD cl_abap_container_utilities=>fill_container_c
    168
    EXPORTING
    169
    im_value     = <l_s_data>
    170
    IMPORTING
    171
    ex_container = l_string.
    172
    173
    PERFORM wrap_str_to_c255
    174
    USING    l_string
    175
    CHANGING e_t_outdata.
    176
    177
    ENDLOOP.
    178
    179
    ENDFORM.                    " data_wrap_std
    180
    181
    *&      Form  data_wrap_uc
    182
    183
          text
    184
    185
         -->P_I_T_DATA  text
    186
         <--P_E_OUTDATA_UC  text
    187
    188
    FORM data_wrap_uc
    189
    USING    i_t_data      TYPE STANDARD TABLE
    190
    i_compress    TYPE rs_bool
    191
    CHANGING e_outdata_uc  TYPE xstring.
    192
    193
    IF i_compress = rs_c_true.
    >>>>>
    EXPORT rsdri = i_t_data
    195
    TO DATA BUFFER e_outdata_uc
    196
    COMPRESSION ON.
    197
    ELSE.
    198
    EXPORT rsdri = i_t_data
    199
    TO DATA BUFFER e_outdata_uc
    200
    COMPRESSION OFF.
    201
    ENDIF.
    202
    203
    IF sy-subrc <> 0.
    204
       RAISE conversion_error.
    205
    ENDIF.
    206
    207
    ENDFORM.                    " data_wrap_uc
    208
    209
    210
    FORM data_wrap_250
    211
    212
    213
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    1
    SY-TABIX
    0
    SY-DBCNT
    1
    SY-FDPOS
    25
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    CPIC- und RFC-Steuerung
    SY-MSGTY
    E
    SY-MSGID
    BL
    SY-MSGNO
    209
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080411
    SY-UZEIT
    163555
    SY-XPROG
    SAPLRSDRI
    SY-XFORM
    RSDRI_INFOPROV_READ_RFC
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    7 FORM         SAPLRSDRI_SERVICES                  LRSDRI_SERVICESF01                    194
    DATA_WRAP_UC
    6 FUNCTION     SAPLRSDRI_SERVICES                  LRSDRI_SERVICESU04                     29
    RSDRI_DATA_WRAP
    5 FORM         GP49E5DYREKDNLT28VWMJJ5FAZY         GP49E5DYREKDNLT28VWMJJ5FAZY           199
    INFOPROV_READ_RSDRI
    4 FUNCTION     SAPLRSDRI                           LRSDRIU02                             153
    RSDRI_INFOPROV_READ_RFC
    3 FORM         SAPLRSDRI                           LRSDRIU02                               1
    RSDRI_INFOPROV_READ_RFC
    2 FORM         SAPMSSY1                            SAPMSSY1                               85
    REMOTE_FUNCTION_CALL
    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
    %_RFC_START
    Chosen variables
    Name
    Val.
    No.       7 Ty.          FORM
    Name  DATA_WRAP_UC
    SYST-REPID
    SAPLRSDRI_SERVICES
    5454554545545544452222222222222222222222
    310C23429F352693530000000000000000000000
    I_COMPRESS
    X
    5
    8
    RS_C_TRUE
    X
    5
    8
    SY
    ###############################################################################À##############
    0000000000000000000000000000000000000000000000010000000000000000000000000000000C00000000000000
    0001000000000000000000000000000000000000000100090001000000010000000000000000002000000000000000
    I_T_DATA
    Table IT_4214[3004988x1456]
    PROGRAM=GP49E5DYREKDNLT28VWMJJ5FAZYFORM=INFOPROV_READ_RSDRIDATA=L_T_DATA
    Table reference: 245
    TABH+  0(20) = C0000005B3A98DB0000000000000000000000000
    TABH+ 20(20) = 000000F500001076002DDA3C000005B0FFFFFFFF
    TABH+ 40(16) = 0400002A00000B10000824C401800000
    store        = 0xC0000005B3A98DB0
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 245   (0x000000F5)
    label        = 4214  (0x00001076)
    fill         = 3004988 (0x002DDA3C)
    leng         = 1456  (0x000005B0)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000040
    occu         = 8     (0x00000008)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xC0000009BB9B2090
    pgHook       = 0x600000008EAEC160
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 3503  (0x00000DAF)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 3014656 (0x002E0000)
    lineAlloc    = 3004992 (0x002DDA40)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    %_DUMMY$$
    2222
    0000
    E_OUTDATA_UC
    ÿ#######1100####ÒWÜ#####°ï6=³$Ç~ßsæ#ä5L#¼ -^##há#°#!&ß3#ð#ô#Á#p6##Òâ¬###Å#.À#6²aÀ#kÀ6´1ÀOp##ú#
    F000008033330000D5D01190BE33B2C7D7E8E348BA25816E8B822D30F8F1C07321DEA019C12C93B6C86C3B3C4700F0
    F61122001100000027C52FD20F6D347EF36545C1C0DE008100016F3B064D13063B22C59855E056210BB06410F019A0
    SYST
    ###############################################################################À##############
    0000000000000000000000000000000000000000000000010000000000000000000000000000000C00000000000000
    0001000000000000000000000000000000000000000100090001000000010000000000000000002000000000000000
    No.       6 Ty.          FUNCTION
    Name  RSDRI_DATA_WRAP
    I_COMPRESS
    X
    5
    8
    I_RESULT250
    2
    0
    I_T_DATA
    Table IT_4214[3004988x1456]
    I_UNICODE_RESULT
    X
    5
    8
    E_OUTDATA_UC
    ÿ#######1100####ÒWÜ#####°ï6=³$Ç~ßsæ#ä5L#¼ -^##há#°#!&ß3#ð#ô#Á#p6##Òâ¬###Å#.À#6²aÀ#kÀ6´1ÀOp##ú#
    F000008033330000D5D01190BE33B2C7D7E8E348BA25816E8B822D30F8F1C07321DEA019C12C93B6C86C3B3C4700F0
    F61122001100000027C52FD20F6D347EF36545C1C0DE008100016F3B064D13063B22C59855E056210BB06410F019A0
    E_T_OUTDATA
    Table[initial]
    E_T_OUTDATA250
    Table[initial]
    RS_C_FALSE
    2
    0
    SY-REPID
    SAPLRSDRI_SERVICES
    5454554545545544452222222222222222222222
    310C23429F352693530000000000000000000000
    No.       5 Ty.          FORM
    Name  INFOPROV_READ_RSDRI
    SY-SUBRC
    0
    0000
    0000
    SY-REPID
    GP49E5DYREKDNLT28VWMJJ5FAZY
    4533434554444453355444344552222222222222
    7049554925B4EC42867DAA561A90000000000000
    SY
    ###############################################################################À##############
    0000000000000000000000000000000000000000000000010000000000000000000000000000000C00000000000000
    0001000000000000000000000000000000000000000100090001000000010000000000000000002000000000000000
    %_DUMMY$$
    2222
    0000
    %_SPACE
    2
    0
    SYST-REPID
    GP49E5DYREKDNLT28VWMJJ5FAZY
    4533434554444453355444344552222222222222
    7049554925B4EC42867DAA561A90000000000000
    I_OUTU
    X
    5
    8
    RS_C_TRUE
    X
    5
    8
    L_T_DATA
    Table IT_4214[3004988x1456]
    E_RFCOUT_UC
    ÿ#######1100####ÒWÜ#####°ï6=³$Ç~ßsæ#ä5L#¼ -^##há#°#!&ß3#ð#ô#Á#p6##Òâ¬###Å#.À#6²aÀ#kÀ6´1ÀOp##ú#
    F000008033330000D5D01190BE33B2C7D7E8E348BA25816E8B822D30F8F1C07321DEA019C12C93B6C86C3B3C4700F0
    F61122001100000027C52FD20F6D347EF36545C1C0DE008100016F3B064D13063B22C59855E056210BB06410F019A0
    I_S_RFCMODE
    0.0.0.1.
    22222222222222222222222222222222222222220000
    00000000000000000000000000000000000000000000
    I_S_RFCMODE-RFC_RECEIVER
    222222222222222222222222222222
    000000000000000000000000000000
    E_EOD
    X
    5
    8
    I_S_RFCMODE-ID
    2222222222
    0000000000
    No.       4 Ty.          FUNCTION
    Name  RSDRI_INFOPROV_READ_RFC
    I_AUTHORITY_CHECK
    R
    5
    2
    I_CURRENCY_CONVERSION
    X
    5
    8
    I_DEBUG
    2
    0
    I_FILENAME
    222222222222222222222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000000000000000000000
    I_INFOPROV
    B100_CB3E
    433354434222222222222222222222
    2100F3235000000000000000000000
    I_MAXROWS
    0
    0000
    0000
    I_READ_ODS_DELTA
    2
    0
    I_REFERENCE_DATE
    20080411
    33333333
    20080411
    I_RESULTTYPE
    U
    5
    5
    I_ROLLUP_ONLY
    X
    5
    8
    I_SAVE_IN_FILE
    2
    0
    I_SAVE_IN_TABLE
    2
    0
    I_S_RFCMODE
    0.0.0.1.
    22222222222222222222222222222222222222220000
    00000000000000000000000000000000000000000000
    I_TABLENAME
    222222222222222222222222222222
    000000000000000000000000000000
    I_USE_AGGREGATES
    X
    5
    8
    I_USE_DB_AGGREGATION
    X
    5
    8
    E_AGGREGATE
    B100_CB3E$X
    433354434252222222222222222222
    2100F3235480000000000000000000
    E_END_OF_DATA
    X
    5
    8
    E_RFCDATA_UC
    ÿ#######1100####ÒWÜ#####°ï6=³$Ç~ßsæ#ä5L#¼ -^##há#°#!&ß3#ð#ô#Á#p6##Òâ¬###Å#.À#6²aÀ#kÀ6´1ÀOp##ú#
    F000008033330000D5D01190BE33B2C7D7E8E348BA25816E8B822D30F8F1C07321DEA019C12C93B6C86C3B3C4700F0
    F61122001100000027C52FD20F6D347EF36545C1C0DE008100016F3B064D13063B22C59855E056210BB06410F019A0
    E_SPLIT_OCCURRED
    2
    0
    E_T_FIELD[]
    Table IT_4[180x40]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_E_T_FIELD
    Table reference: 4
    TABH+  0(20) = C0000005B3902040C0000005B38D281000000000
    TABH+ 20(20) = 0000000400000004000000B400000028FFFFFFFF
    TABH+ 40(16) = 0400000100000F700010249401800000
    store        = 0xC0000005B3902040
    ext1         = 0xC0000005B38D2810
    shmId        = 0     (0x00000000)
    id           = 4     (0x00000004)
    label        = 4     (0x00000004)
    fill         = 180   (0x000000B4)
    leng         = 40    (0x00000028)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000060
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xC0000005B39020A0
    pgHook       = 0xC0000005B38FC770
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 16    (0x00000010)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 304   (0x00000130)
    lineAlloc    = 304   (0x00000130)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xC0000005B38D27A0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC0000005B38D2740
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    E_T_RFCDATA[]
    Table IT_5[0x256]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_E_T_RFCDATA
    Table reference: 5
    TABH+  0(20) = 0000000000000000C0000005B38D292000000000
    TABH+ 20(20) = 00000005000000050000000000000100FFFFFFFF
    TABH+ 40(16) = 0400000100000E580010249401800000
    store        = 0x0000000000000000
    ext1         = 0xC0000005B38D2920
    shmId        = 0     (0x00000000)
    id           = 5     (0x00000005)
    label        = 5     (0x00000005)
    fill         = 0     (0x00000000)
    leng         = 256   (0x00000100)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000055
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xC0000005B38D28B0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC0000005B38D2850
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    E_T_RFCDATAV[]
    Table IT_6[0x100]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_E_T_RFCDATAV
    Table reference: 6
    TABH+  0(20) = 0000000000000000C0000005B38D2A3000000000
    TABH+ 20(20) = 00000006000000060000000000000064FFFFFFFF
    TABH+ 40(16) = 0400000100000F000010249401800000
    store        = 0x0000000000000000
    ext1         = 0xC0000005B38D2A30
    shmId        = 0     (0x00000000)
    id           = 6     (0x00000006)
    label        = 6     (0x00000006)
    fill         = 0     (0x00000000)
    leng         = 100   (0x00000064)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000058
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xC0000005B38D29C0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC0000005B38D2960
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    I_T_RANGE[]
    Table IT_0[24x153]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_I_T_RANGE
    Table reference: 0
    TABH+  0(20) = C0000005B38C97E0C0000005B38C97A000000000
    TABH+ 20(20) = 00000000000000000000001800000099FFFFFFFF
    TABH+ 40(16) = 04000001000004B80010249421800000
    store        = 0xC0000005B38C97E0
    ext1         = 0xC0000005B38C97A0
    shmId        = 0     (0x00000000)
    id           = 0     (0x00000000)
    label        = 0     (0x00000000)
    fill         = 24    (0x00000018)
    leng         = 153   (0x00000099)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000011
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xC0000005B38C9840
    pgHook       = 0xC0000005B38CA1F0
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 2     (0x00000002)
    refCount     = 1     (0x00000001)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 48    (0x00000030)
    lineAlloc    = 48    (0x00000030)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 3     (0x00000003)
    >>>>> 1st level extension part <<<<<
    regHook      = 0xC0000005B3AB3F70
    collHook     = 0x0000000000000000
    ext2         = 0xC0000005B38C9730
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC0000005B38C96D0
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    I_T_REQUID[]
    Table IT_7[0x12]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_I_T_REQUID
    Table reference: 7
    TABH+  0(20) = 0000000000000000C0000005B38D2B4000000000
    TABH+ 20(20) = 0000000700000007000000000000000CFFFFFFFF
    TABH+ 40(16) = 04000001000006780010249401800000
    store        = 0x0000000000000000
    ext1         = 0xC0000005B38D2B40
    shmId        = 0     (0x00000000)
    id           = 7     (0x00000007)
    label        = 7     (0x00000007)
    fill         = 0     (0x00000000)
    leng         = 12    (0x0000000C)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000019
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xC0000005B38D2AD0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC0000005B38D2A70
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    I_T_RTIME[]
    Table IT_1[3x121]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_I_T_RTIME
    Table reference: 1
    TABH+  0(20) = C0000005B38CB680C0000005B38CB64000000000
    TABH+ 20(20) = 00000001000000010000000300000079FFFFFFFF
    TABH+ 40(16) = 04000001000005980010249401800000
    store        = 0xC0000005B38CB680
    ext1         = 0xC0000005B38CB640
    shmId        = 0     (0x00000000)
    id           = 1     (0x00000001)
    label        = 1     (0x00000001)
    fill         = 3     (0x00000003)
    leng         = 121   (0x00000079)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000015
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xC0000005B38CB6E0
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 3     (0x00000003)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xC0000005B38CB5D0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC0000005B38CB570
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    I_T_SFC[]
    Table IT_2[17x52]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_I_T_SFC
    Table reference: 2
    TABH+  0(20) = C0000005B38CBFA0C0000005B38CBF6000000000
    TABH+ 20(20) = 00000002000000020000001100000034FFFFFFFF
    TABH+ 40(16) = 0400000100000DB00010249401800000
    store        = 0xC0000005B38CBFA0
    ext1         = 0xC0000005B38CBF60
    shmId        = 0     (0x00000000)
    i

    Hello,
    did you resolve the problem ?
    Please tell me how if it's resolved.
    Best Regards

  • ABAP Dump analysis problem

    Hi , How to solve ABAP Dump MESSAGE_TYPE_X_TEXT in ST22 ?
    Regards
    ASADUZZAMAN

    MESSAGE_TYPE_X is a dump related to your GUI, upgrade your (or your users) GUI patch to the latest level and that should solve the issue.
    This issue has been discussed previously in several occations, please search before posting
    Regards
    Juan

  • ABAP dump  DDIC_TYPE_INCONSISTENCY

    Hi Expert,
    we are getting the below abap dump  DDIC_TYPE_INCONSISTENCY frequently.
    Runtime Errors         DDIC_TYPE_INCONSISTENCY
    Date and Time          10.06.2008 12:11:34
    What can you do?
         Note which actions and input led to the error.
         For further help in handling the problem, contact your SAP administrator
        You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
    Error analysis
         There is an internal system error.
         eliminated with ABAP/4.
    How to correct the error
         The internal system error cannot be fixed by ABAP means only.
         You may be able to find a solution in the SAP note system. If you have
         access to the SAP note system, try searching for the following terms:
          "DDIC_TYPE_INCONSISTENCY" " "
          "SAPLMEACCTVI" or "LMEACCTVITOP"
         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:
         "DDIC_TYPE_INCONSISTENCY" " "
         "SAPLMEACCTVI" or "LMEACCTVITOP"
         If you cannot solve the problem yourself and want to send an error
         notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    Please help me to fix this issue.
    Thanks & Regards,
    Reddy V

    Hi Antoni,
    Please note the below sm21 log
    Details Page 2 Line 27 System Log: Local Analysis of UBSDEV                   1
    Time     Type  Nr   Clt   User   TCode   Grp N      Text
    12:11:34 DIA   001  120 VSALI            AB  0       Run-time error   "DDIC_TYPE_INCONSISTENCY" occurred
    Run-time error "DDIC_TYPE_INCONSISTENCY" occurred
    Details
    Recording at local and central time........................ 10.06.2008 12:11:34
    Task...... Process                     User...... Terminal Session TCode Program Cl Problem cl          Package
    29480      Dialog work process No. 001 VSALI      acerdev0       1               T  Transaction Problem SABP
    Further details for this message type
    Module nam   Line     Error text
    abucutil        1053  ab_RxDdicTypeError
    Documentation for system log message AB 0 :
    The specified runtime error has occurred in the system.
    Parameter
    abcdefghijklmnopqrstuvwxyz .. DDIC_TYPE_INCONSISTENCY
    Technical details
    File  Offset   RecFm    System log type        Grp     N  
    40    319860   l            Error (Module, Row)    AB     0 
    variable message data
    ab_RxDdicTypeError                                  abucutil1053
    Regards,
    Reddy V

  • In XD02/03, while viewing customer master, abap dump is coming.

    While executing transaction xd02/03 for certain customers, system throws ABAP dump "internal error DB and COMM_A_MEMORY incompatible. Can anybody know how to fix such issue. The issue seems to be related to Addres number that we enter while master creation.

    Hi
    Have you tried updating the table using update command. Because of this the system is generating the dump.
    Please check this note 436119
    serious problem in vendor master data fk03
    Regards
    Shiva

Maybe you are looking for