Dump in Production due to CALL_FUNCTION_OPEN_ERROR???

Hi all,
I am getting lot of dumps in Production with following details
What happened?
Error in ABAP application program.
The current ABAP program "SAPLOLEA" 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 error occurred when executing a Remote Function Call.
"Protocol error when communicating with SAPGUI."
Status of connection.... "RFC DRV=GUI INPUT"
Internal error code.... "RFC_IO20"
When communicating with SAPGUI, a protocol error was detected.
Any have Idea for this ?

Dear Vipin
That is a very complicated error, difficult to analyze.
First I would recommend an update of the SAP GUI onto the newest patch
level. Additionally please update the SAP kernel to the latest patchlevel and the RFC libraries!
If that all should not help, deeper analyses are to be made so in your system.
For that you should then create a support message.
Best regards
Sven

Similar Messages

  • ZReport getting dump in Production but not in Quality and development

    Hi,
    There isa Zreport which displays daily stock  in PP module.
    It is getting dump in Production not in quality and development.
    Since four days it is getting dump. Before that it is fine.
    Please any one guide How to resolve.
    Advance Thanks.

    Runtime Error          SAPSQL_IN_ITAB_ILLEGAL_OPTION
           Occurred on     29.08.2007 at   08:50:13
    <u>Invalid value in OPTION field of value table for IN itab operator.</u>
    What happened?
    <b>Error in ABAP application program.</b>
    The current ABAP program "ZPPRDR417" had to be terminated because o
    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 admin
    termination messages, especially those beyond their normal deletio
    date.
    <b>Error analysis</b>
    The current ABAP/4 program attempted to execute an ABAP/4 Open SQL
    statement in which the WHERE condition contains an IN itab operator
    The IN itab operator is used with internal tables which
    have the following structure:
       SIGN(1)   OPTION(2)   LOW LIKE db_field   HIGH LIKE db_field
    The OPTION column should contain only one of the following values:
       "EQ LE GE CP BT NE LT GT NP NB"
    The value " " is not allowed here.
    <b>How to correct the error</b>
    Use only one of the permitted values in the OPTION column.
    Information on where terminated
    The termination occurred in the ABAP program "ZPPRDR417" in "WIP_STOCK_REP
    The main program was "ZPPRDR417 ".
    The termination occurred in line 330 of the source code of the (Include)
    program "ZPPRDR417_FORM"
    of the source code of program "ZPPRDR417_FORM" (when calling the editor 33
    Source code extract
    Caution: Program has changed
    Caution: At time of termination,  Active source code no longer available
    003000 ?   r_bwart-low  =  '106'.
    003010 ?   append r_bwart.
    003020 ?
    003030 ?   r_bwart-low  =  '124'.
    003040 ?   append r_bwart.
    003050 ?
    003060 ?   r_bwart-low  =  '125'.
    003070 ?   append r_bwart.
    003080 ?
    003090 ?   select matnr
    003100 ?          werks
    003110 ?     into table i_marc
    003120 ?     from marc
    003130 ?    where ( matnr LIKE 'BILC%'
    003140 ?       OR   matnr LIKE 'LGN%'
    003150 ?       OR   matnr LIKE 'BRN%'
    003160 ?       OR   matnr LIKE 'EBB%' )
    003170 ?       AND  matnr NE 'BRN_DECLASSE'
    003180 ?       AND  matnr NE 'BRN_SAF'
    003190 ?       and  werks in r_werks.
    003200 ?
    003210 ?   r_material-sign = 'I'.
    003220 ?   r_material-option = 'EQ'.
    003230 ?
    003240 ?   loop at i_marc into wa_marc.
    003250 ?     r_material-low  = wa_marc-matnr.
    003260 ?     append r_material.
    003270 ?   endloop.
    003280 ?   clear r_material.
    003290 ?
         > ?   if not i_matdoc is initial.
    003310 ?    select MBLNR
    003320 ?           MJAHR
    003330 ?           ZEILE
    003340 ?           BWART
    003350 ?           MATNR
    003360 ?           WERKS
    003370 ?           SHKZG
    003380 ?           MENGE
    003390 ?           UMWRK
    003400 ?      into table i_mseg_qty
    003410 ?      from mseg
    003420 ?       for all entries in i_matdoc
    003430 ?     where MBLNR eq i_matdoc-MBLNR
    003440 ?       and MJAHR eq i_matdoc-MJAHR
    003450 ?       and BWART in r_bwart
    003460 ?       and matnr in r_material
    003470 ?       and werks in r_werks.
    003480 ?
    003490 ?    sort i_mseg_qty by matnr.

  • CX_SY_FILE_OPEN_MODE - short dump on production but not in Dev and Test

    Hello,
    I'm getting the follwoing short dump in production when I run the program which writes the data to application server. I have open data set and close data set. Same program when I in development and test I do not get any short dump. Can any know what could be cause for this.
    CX_SY_FILE_OPEN_MODE
    Copy paste of error analysis from ST22 short dump -
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_FILE_OPEN_MODE', was not
         caught in
        procedure "DATA_UPLOAD_APP_SERVER" "(FORM)", nor was it propagated by a RAISING
         clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        When accessing the file "/bw/FTPOUT/BPR/OTHER/test.csv", the system recognized
         that this file is
        not open. Therefore, the file cannot be accessed.

    The file could not be OPENed in your production system for a variety of reasons - no authorization, file doesn't exist etc. You should have check sy-subrc right after OPEN DATASET and if not zero, yous should not TRANSFER or READ the file and instead you should have given a message with sy-msgid and sy-msgno which would give you the reason. The dump here is simply saying that OPEN is unsuccessful, so any subsequent READ or TRANSFER would throw runtime dump, if done after an unsuccessful OPEN.

  • Sir / Madam        Actually I am willing to buy Apple (MD101HN/A) 13" MacBook Pro with Retina Display 2.6GHz. I am from siliguri, Dist Darjeeling, West Bengal, India. But currently i am unable to buy your product due to unavailability of your mentioned pr

    Sir / Madam
          Actually I am willing to buy Apple (MD101HN/A) 13" MacBook Pro with Retina Display 2.6GHz.
    I am from siliguri, Dist Darjeeling, West Bengal, India. But currently i am unable to buy your product due to unavailability of your mentioned product in India. so can you please inform me at least a confirmed date when will be the product available. because it's really a urgent for me. So please give a reply with a confirm date.
    Yours Faithfully
    Saikat Nath.

    This board is just other users, there's no one here from Apple to answer a question like that. Sorry.

  • How to download run time ABAP dump in production environment

    Hello,
    I am getting run time ABAP dump in production environment. Please guide me onHow to download run time ABAP dump in production environment?
    Also, please tell me how best can analyze that dump. Like there are tools like gdb, purify etc. to analyze problems in other languages.
    Regards,
    Sameer.

    Hi,
    Go to ST22, and Double click on the error line, It will show you the detailed analysis.
    See the section How to correct the error for details on error correction and the instructions to download the log( you can download in the format you want - HTML would be a nice option).
    And there are no tools to analyze errors but ST22 has a large data regarding the location of the error, the reason and the source code which caused. So you need to use the debugger to reproduce the error and check the source code,
    Regards
    Karthik D

  • I did not keep the email with my registration for the free trial so I do not have a serial number as I have no products due to the fact that my trial has expired but I would now like to purchase a product and I cannot skip the serial number request.

    I did not keep the email with my registration for the free trial so I do not have a serial number as I have no products due to the fact that my trial has expired but I would now like to purchase a product and I cannot skip the serial number request in order to buy the product it's so irritating I'm about to just do a different product altogether... anyone know how to get or bypass the serial number request?

    You must first make the purchase, then you will receive the serial number you are asking about.  YOu do not acquire the serial number thru the software.  You acquire it thru the purchase, possibly via a follow-up confirmation  email.

  • Dump in production

    hi floks,
    We have created one new DSO and moved to Production system. When we did data load and try activating the request we are getting a short dump. The screen shots are attached here with.
    We did not face any problems in D and Q systems. Please let me know if you need any other information on this.

    Hi,
    may be the data volume is high and also due to non availability of background process.  Try reactivating the request in Prod.
    Mostly it will occur due to no background process availability.
    Let us know the details.
    Reg
    Pra

  • Dump in production system

    Hi Experts,
    I got following error description in ST22.plz can anyone tell m
    what will be the probable reason for this dump. How should i correct it?
    Where i need to check?
    Errore run-time        DBIF_REPO_PART_ALREADY_EXISTS
    Analysis:
    Internal problem: You attempted to insert a program which already
    exists partially at least. This is probably due to an inconsistency in the  database tables.

    hi Sheetal,
    What happened is your Basis guy might have not imported this TR properly.
    I will tell what would have been your scenario. There is a program in production.
    You deleted that program in developement and recreated the same and you moved it to production under one TR. Correct me if I am wrong in any of above.
    Just ask your Basis to import this TR with overwrite option checked.
    Reward all useful answers.
    Regards,
    Atish

  • TSV_TNEW_PAGE_ALLOC_FAILED  Dump in Production BW 3.5 system

    Hi Basis Gurus,
    In our production BW 3.5 system we are getting dump in ST22.
    The dump is TSV_TNEW_PAGE_ALLOC_FAILED
    Please let me know what could be the reason for this dump and why we are getting it.
    I tried searching in service market place and there we can find lot of things related to this dump.But not sure which one is specificaly related to this dump.
    Our system details are as follows
    BW 3.5
    Solaris OS
    Oracle Database.
    Please help me in resolving this dump.
    Regards,
    Anil.

    Hello Anil,
    what is the frequency of these dumps.
    If the dump once in a while,you can simply ignore it
    If frequency is more....you will need to reasrch a bit before increasing the paging memory as suggested previously
    Just check what program is causing the dump,is it SAP standard program or a z program created by your developers.
    If it is a SAP standard program just search on market place and look if any new version of the program exists which is tuned better and which consumes less memory
    If it is a z program ask your developer to tune the program(this can be a highly cause of this dump as programs created usually consume a lot of memory due to which this dump occurs)
    If none of these help,go for increase in the paging memory as previusly suggested
    Rohit

  • Short dump on production server

    ABAP runtime errors    GETWA_NOT_ASSIGNED
           Occurred on     28.12.2007 at 11:16:11
    >> Short dump has not been completely stored. It is too big.
    Field symbol has not yet been assigned.
    What happened?
    The current ABAP/4 program "SAPLCEI0 " had to be terminated because
    one of the statements could not be executed.
    This is probably due to an error in the ABAP/4 program.
    What can you do?
    Note the actions and input that caused the error.
    Inform your SAP system administrator.
    You can print out this message by choosing "Print". Transaction ST22
    allows you to display and manage termination messages, including keeping
    them beyond their normal deletion date.
    Error analysis
    You attempted to access an unassigned field symbol
    (data segment 2941).
    This error occurs:
    - if you address a typed field symbol before it has been set with
      ASSIGN or
    - if you address a field symbol that has been reset with UNASSIGN
      or pointed to a local field that no longer exists, or
    - if you address a field symbol that pointed to a line of an internal
      table that has now been deleted, or
    - if you address a global function interface partameter, even
      though the relevant function module is not active,
      i.e. it is not in the list of active calls. You can get the list
      of active calls from the this short dump.
    How to correct the error
    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:
    "GETWA_NOT_ASSIGNED"
    "SAPLCEI0 " or "LCEI0U29 "
    "CEI0_DDB_HAS_VALUES_INTERNAL"
    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.............. "46C"
    Application server....... "SAPCLUN"
    Network address.......... "172.18.112.20"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "16x Intel 80158"
    Database server.......... "DBCLUN"
    Database type............ "MSSQL"
    Database name............ "PRD"
    Database owner........... "dbo"
    Character set............ "English_United State"
    SAP kernel............... "46D"
    Created on............... "Apr 9 2006 21:37:58"
    Created in............... "NT 4.0 1381 Service Pack 6 x86 MS VC++ 12.00"
    Database version......... "SQL_Server_7.00 "
    Patch level.............. "2225"
    Patch text............... " "
    Supported environment....
    Database................. "MSSQL 6.5.213 or higher, MSSQL 7.0.1 or higher"
    SAP database version..... "46D"
    Operating system......... "Windows NT 4.0, Windows NT 5.0, Windows NT 5.1,
    Windows NT 5.2, , System build information:,
    , LCHN : "
    User, transaction...
    Client.............. 400
    User................ "QPBASIC"
    Language key........ "E"
    Transaction......... "QA02 "
    Program............. "SAPLCEI0 "
    Screen.............. "SAPLQPL1 0200"
    Screen line......... 34
    Information on where termination occurred
    The termination occurred in the ABAP/4 program "SAPLCEI0 " in
    "CEI0_DDB_HAS_VALUES_INTERNAL".
    The main program was "SAPLQPL1 ".
    The termination occurred in line 49
    of the source code of program "LCEI0U29 " (when calling the editor 490).
    Source code extract
    000190   *"  EXCEPTIONS
    000200   *"      NOT_FOUND
    000210   *"----
    000220
    000230     DATA:
    000240           ls_charac TYPE api_char,
    000250           lt_charac TYPE STANDARD TABLE OF api_char,
    000260           ls_vali   TYPE api_vali.
    000270
    000280     DATA: ls_mi        TYPE ts_mi,
    000290           ls_wi        TYPE ts_wi,
    000300           ls_icv       TYPE ts_value,
    000310           ls_defval    TYPE ts_defval,
    000320           ls_inco_val  TYPE ts_inco_val,
    000330           ls_char_list TYPE ts_char_list,
    000340           lv_subrc     TYPE sy-subrc,
    000350           lv_kntype    TYPE cukntype.
    000360
    000370   data: ls_vallist   TYPE ddb_c04,                             "676840
    000380         lt_vallist   TYPE STANDARD TABLE OF ddb_c04,           "676840
    000390         ls_restrict  type ddb_c03,                             "699141
    000400         lt_restrict  type STANDARD TABLE OF ddb_c03,           "699141
    000410         lv_rflag       type c.                                 "676840
    000420
    000430   *----
    000440     REFRESH exp_values.
    000450
    000460     DESCRIBE TABLE imp_characteristics LINES sy-tfill.
    000470     IF sy-tfill EQ 0.
    000480       LOOP AT
            INTO   ls_char_list.
    000500         ls_charac-atinn = ls_char_list-atinn.
    000510         APPEND ls_charac TO lt_charac.
    000520       ENDLOOP.
    000530     ELSE.
    000540       lt_charac = imp_characteristics[].
    000550     ENDIF.
    000560
    000570     LOOP AT   lt_charac
    000580          INTO ls_charac.
    000590       IF ls_charac-atnam NE space.
    000600   *     input: name
    000610         PERFORM read_mi_with_atnam
    000620                 USING
    000630                   ls_charac-atnam
    000640                 CHANGING
    000650                   lv_subrc
    000660                   ls_mi.
    000670       ELSE.
    000680   *     input: atinn
    Contents of system fields
    SY field contents..................... SY field contents.....................
    SY-SUBRC 0                             SY-INDEX 0
    SY-TABIX 0                             SY-DBCNT 1
    SY-FDPOS 1                             SY-LSIND 0
    SY-PAGNO 0                             SY-LINNO 1
    SY-COLNO 1
    Chosen variables
    Name.......................... Contents.1........2........3....+....4
    PROP_BITMAP                    310
                                   3000
                                   6100
    ALLOWED_VALUES
                                   2
                                   0
    PROP_WIDTH                     300
                                   2000
                                   C100
    ASSIGNED_VALUES                X
                                   5
                                   8
    TOP_WINDOW                     33
                                   2000
                                   1000
    ASSIGNED_VALUES_API_DI
                                   2
                                   0
    PROP_INDEX                     350
                                   5000
                                   E100
    DEFAULT_VALUES
                                   2
                                   0
    DYNPRO_9                       19
                                   1000
                                   3000
    DEFAULT_VALUES_API_DN
                                   2
                                   0
    DYNPRO_8                       18
                                   1000
                                   2000
    DEFAULT_VALUES_API_ST
                                   2
                                   0
    DYNPRO_7                       17
                                   1000
                                   1000
    DOCUMENT_INFO
                                   2
                                   0
    PROP_SOUND                     340
                                   5000
                                   4100
    FIRST_ASSIGNED_VALUE
                                   2
                                   0
    PROP_TEXT                      330
                                   4000
                                   A100
    INCONSISTENT_VALUES
                                   2
                                   0
    LANGUAGE                       E
                                   4
                                   5
    SY-LANGU                       E
                                   4
                                   5
    PROP_BITMAP_STYLE              320
                                   4000
                                   0100
    VALID_VALUES
                                   2
                                   0
    PROP_FONT_SIZE                 380
                                   7000
                                   C100
    EXP_VALUES[]                   #########################À##°###########
                                   0000000000000000000000000C00B00000000000
                                   00000000000000000000000040000A0000000000
    ... +  40                      ################ÿÿÿÿ####################
                                   0000000000000000FFFF00000000000000000000
                                   1000000000001000FFFF81007000430000000000
    ... +  80                      ################################
                                   00000000000000000000000000008000
                                   00000000000000000000000000004100
    PROP_ITEM                      370
                                   7000
                                   2100
    IMP_CHARACTERISTICS[]          #########################À##############
                                   0000000000000000000000000C00800000000000
                                   00000000000000000000000040000A0000000000
    ... +  40                      ################ÿÿÿÿI###################
                                   1000000000000000FFFF40000000000000000000
                                   0000000000000000FFFF90002000430000000000
    ... +  80                      ################################
                                   00000000000000000000000000008000
                                   00000000000000000000000000005100
    SCREEN-ACTIVE                  0
                                   3
                                   0
    SY-XPROG                       SAPCNVE
                                   5454454222222222222222222222222222222222
                                   3103E65000000000000000000000000000000000
    TVS_EDITLABELS                 6
                                   0000
                                   6000
    SY-TFILL                       0
                                   0000
                                   0000
    INCL_PRICE                     0000
                                   3333
                                   0000
    LS_CHAR_LIST                   00000000000000000000
                                   3333333333333333333322222222222
                                   0000000000000000000000000000000
    RSJOBINFO                                                      00000000
                                   2222222222222222222222222222222233333333
                                   0000000000000000000000000000000000000000
    ... +  40                      000000
                                   3333332222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  80                      ####
                                   0000
                                   0000
    SYST                           ########################################
                                   0000000000000000000000000000000000000000
                                   0000000000000000000000000000000000000000
    ... +  40                      ####################################I###
                                   0000000000000000000000000000000000004000
                                   1000100010000000100000000000000000009000
    ... +  80                      ########################################
                                   0000000000000000100000000000000000000000
                                   0000000000000000E00000000000000000000000
    ... + 120                      ####################################p###
                                   00000000
                                   0000000
    LT_CHARAC                      Table[initial]
                                   0000FFFD
                                   0000FFFF
    LS_CHARAC                      0000000000
                                   3333333333222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   222222222222222222222222222222222
                                   000000000000000000000000000000000
    SPACE
                                   2
                                   0
    Active calls / events
    No.... Type........ Name..........................
           Programm
           Include                                  Line
         1 FUNCTION     CEI0_DDB_HAS_VALUES_INTERNAL
           SAPLCEI0
           LCEI0U29                                    49
         2 FUNCTION     QMCF_CONFIGURATION_READ
           SAPLQMCF
           LQMCFU02                                    61
         3 FUNCTION     QMCF_SPECIFICATION_CONFIG_READ
           SAPLQMCF
           LQMCFU01                                    60
         4 FUNCTION     QPAP_PLAN_READ
           SAPLQPAP
           LQPAPU02                                   297
         5 FUNCTION     QEEV_TABLES_GENERATE
           SAPLQEEV
           LQEEVU01                                   118
         6 FORM         MERKMALSSAETZE_ANLEGEN
           SAPLQPL1
           LQPL1F12                                    85
         7 FORM         ST_RECHNE_571
           SAPLQPL1
           LQPL1F1L                                    26
         8 FORM         OK_PROBENBERECHNUNG
           SAPLQPL1
           LQPL1F1W                                    23
         9 FORM         FCODE_BEARBEITEN
           SAPLV00F
           LV00FF0F                                    97
        10 FUNCTION     SCREEN_SEQUENCE_CONTROL
           SAPLV00F
           LV00FU02                                    46
        11 FORM         FCODE
           SAPLQPL1
           LQPL1F2D                                    61
        12 MODULE (PAI) FCODE
           SAPLQPL1
           LQPL1I0P                                    11
    Internal notes
    The termination occurred in the function "getwa_abswa" of the SAP
    Basis System, specifically in line 1003 of the module
    "//bas/46D/src/krn/runt/abgetwa.c#20".
    The internal operation just processed is "LOOP".
    The internal session was started at 20071228111310.
    Active calls in SAP kernel
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Callstack without Exception:
    App       : disp+work.EXE (pid=500)
    When      : 12/28/2007 11:16:13.65
    Threads   : 2
    Computer Name       : ELEPRDCI
    User Name           : prdadm
    Number of Processors: 16
    Processor Type: x86 Family 15 Model 4 Stepping 8
    Windows Version     : 5.2 Current Build: 3790
    Stack Dump for Thread Id a5c
    eax=00000000 ebx=000003a8 ecx=00000e58 edx=00000000 esi=000003a8 edi=00000000
    eip=7c82ed54 esp=03138cc4 ebp=03138d34 iopl=0         nv up ei ng nz ac po cy
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000297
    function : KiFastSystemCallRet
             7c82ed54 c3               ret
             7c82ed55 8da42400000000   lea     esp,[esp]              ss:03138cc4=7c822124
             7c82ed5c 8d642400         lea     esp,[esp]              ss:40cd7cc3=????????
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    03138d34 77e6ba12 000003a8 0001d4c0 00000000 03138d6c ntdll!KiFastSystemCallRet
    03138d48 00baaa71 000003a8 0001d4c0 77bf1d88 00000002 kernel32!WaitForSingleObject
    03138d6c 004d113b 004d10fc 77bf1d88 77bf1d88 77bf1d88 disp+work!
    04b5ffb8 77e66063 00215740 00000000 00000000 00215740 MSVCRT!endthreadex
    04b5ffec 00000000 77bcb4bc 00215740 00000000 00000000 kernel32!GetModuleFileNameA
    List of ABAP programs affected
    Type
    Program
    Gen. date  time
    LoadSize
    Prg
    SAPLQPL1
    17.09.2006 09:35:11
    479232
    Prg
    SAPMSSYD
    14.08.2000 15:39:21
    16384
    Prg
    SAPFSYSCALLS
    21.12.1999 19:32:31
    7168
    Prg
    CL_EXITHANDLER================
    18.12.2004 13:14:45
    13312
    Prg
    CL_ABAP_TYPEDESCR=============
    04.01.2000 19:06:00
    17408
    Prg
    CL_ABAP_ELEMDESCR=============
    04.01.2000 19:06:00
    13312
    Prg
    CL_ABAP_DATADESCR=============
    04.01.2000 19:06:00
    11264
    Prg
    CL_ABAP_REFDESCR==============
    04.01.2000 19:06:00
    14336
    Prg
    CL_ABAP_STRUCTDESCR===========
    04.01.2000 19:06:00
    16384
    Prg
    CL_ABAP_COMPLEXDESCR==========
    04.01.2000 19:06:00
    11264
    Prg
    CL_ABAP_TABLEDESCR============
    04.01.2000 19:06:00
    16384
    Prg
    CL_ABAP_CLASSDESCR============
    04.01.2000 19:06:00
    23552
    Prg
    CL_ABAP_OBJECTDESCR===========
    04.01.2000 19:06:00
    28672
    Prg
    CL_ABAP_INTFDESCR=============
    04.01.2000 19:06:00
    21504
    Prg
    IF_EX_INSPECTIONLOT_UPDATE====
    13.07.2002 00:12:42
    5120
    Typ
    SXS_INTER
    30.11.1998 15:55:16
    1024
    Prg
    SAPLSEXV
    17.09.2006 08:50:01
    155648
    Prg
    SAPLSXCH
    18.12.2004 13:22:27
    80896
    Typ
    V_EXT_ACT
    14.10.1999 22:16:55
    2048
    Prg
    CL_EX_INSPECTIONLOT_UPDATE====
    13.07.2002 00:12:42
    26624
    Prg
    SAPLV00F
    08.03.2001 10:01:57
    68608
    Typ
    T185E
    15.07.1997 16:57:08
    2048
    Typ
    T185F
    14.08.1997 21:32:52
    2048
    Typ
    T185
    16.08.2000 11:43:40
    3072
    Typ
    T185V
    10.11.1999 17:45:26
    4096
    Typ
    TQ01
    14.02.1998 14:07:17
    2048
    Prg
    SAPLSTXD
    17.09.2006 08:53:44
    406528
    Prg
    SAPCNVE
    04.01.2000 19:06:37
    7168
    Prg
    SAPLLANG
    04.01.2000 19:06:49
    9216
    Prg
    SAPLV01Z
    17.09.2006 09:34:42
    210944
    Prg
    SAPLCLFM
    17.09.2006 09:34:56
    688128
    Prg
    SAPLCUOB
    17.09.2006 09:18:21
    34816
    Prg
    SAPLCLSE
    13.02.2005 06:50:14
    177152
    Prg
    SAPLCTMS
    17.09.2006 09:34:59
    942080
    Prg
    SAPLCTCV
    17.09.2006 09:27:23
    192512
    Prg
    SAPLCTCF
    12.02.2005 20:42:31
    24576
    Prg
    SAPLV01P
    17.09.2006 09:34:42
    166912
    Prg
    SAPLMFAW
    18.12.2004 14:02:28
    51200
    Typ
    TFAWY
    29.07.1998 19:48:52
    2048
    Typ
    TFAWL
    29.07.1998 19:48:49
    2048
    Typ
    TFAWX
    29.07.1998 19:48:51
    2048
    Typ
    TFAW
    29.07.1998 19:48:45
    2048
    Prg
    RDDFIE00
    04.01.2000 19:06:11
    19456
    Prg
    SAPLQAST
    13.02.2005 07:23:55
    28672
    Prg
    SAPLBSVA
    17.09.2006 09:02:09
    270336
    Prg
    SAPLQSTA
    20.01.2000 10:08:08
    26624
    Typ
    TQ01A
    29.07.1998 19:56:34
    2048
    Prg
    SAPLOMCV
    04.01.2000 19:06:50
    14336
    Typ
    TMCNV
    24.02.1999 03:33:25
    2048
    Prg
    SAPLSCNT
    15.11.2001 05:19:20
    28672
    Prg
    SAPLSVSM
    15.11.2001 05:19:20
    25600
    Prg
    SAPLSGUI
    15.11.2001 05:19:20
    33792
    Prg
    SAPLSTTM
    17.09.2006 08:49:52
    83968
    Prg
    SAPLSBDC
    17.09.2006 08:46:17
    66560
    Prg
    CL_DATAPROVIDER===============
    15.11.2001 05:19:18
    50176
    Typ
    OBJ_RECORD
    14.02.1998 08:30:43
    2048
    Prg
    SAPLSTUP
    17.09.2006 08:46:10
    96256
    Prg
    SAPLCNDP
    17.09.2006 08:53:21
    201728
    Prg
    SAPFGUICNTL
    18.12.2004 11:31:41
    20480
    Prg
    SAPLOLEA
    12.07.2002 21:39:11
    81920
    Prg
    SAPLSFES
    17.09.2006 08:53:22
    164864
    Prg
    SAPLGRFC
    12.07.2002 21:39:11
    16384
    Prg
    SAPSHDTV
    18.12.2004 12:16:52
    36864
    Typ
    SHDSTU
    14.12.1998 23:15:34
    1024
    Typ
    SHDSTCIU
    14.12.1998 23:15:34
    1024
    Prg
    CL_GUI_PROPS_CONSUMER=========
    18.12.2004 11:27:30
    26624
    Prg
    CL_DYNAMIC_GUI_EXTENSIONS=====
    11.02.2000 14:36:06
    55296
    Prg
    CL_GUI_DATAMANAGER============
    18.12.2004 11:34:01
    82944
    Prg
    /1BCDWBEN/SAPLQEN0000
    13.07.2002 02:11:40
    51200
    Prg
    SAPLSENA
    04.01.2000 19:06:53
    28672
    Prg
    SAPLQELA
    17.09.2006 09:27:48
    415744
    Typ
    QALS
    13.07.2002 00:12:42
    27648
    Prg
    SAPLQAUT
    13.02.2005 01:25:27
    177152
    Prg
    SAPLSWUG
    17.09.2006 08:53:33
    264192
    Typ
    SWOTOBJID
    04.05.1995 15:20:52
    2048
    Typ
    SWHACTOR
    04.04.1995 16:18:07
    1024
    Prg
    CL_GOS_MANAGER================
    17.09.2006 08:53:30
    24576
    Prg
    CL_GOS_VIEW_MANAGER===========
    21.12.1999 19:23:29
    29696
    Typ
    SGOS_MVOBJ
    01.12.1999 08:16:05
    2048
    Prg
    SAPLSUU1
    17.09.2006 08:53:37
    183296
    Typ
    USR02
    15.11.2001 05:09:06
    5120
    Typ
    USREFUS
    18.12.2004 11:18:28
    1024
    Prg
    SAPLTHFB
    17.09.2006 08:53:29
    270336
    Typ
    BORIDENT
    28.08.1997 08:38:50
    1024
    Prg
    CL_GOS_TOOLBOX_MODEL==========
    17.09.2006 08:53:30
    39936
    Typ
    SGOS_MODL
    08.02.2000 16:42:30
    3072
    Prg
    SAPLBDLS
    14.08.2000 15:20:53
    13312
    Typ
    T000
    11.09.1997 10:17:18
    3072
    Prg
    CL_GOS_PUBLICATION============
    17.09.2006 08:53:30
    24576
    Prg
    CL_GUI_OBJECT=================
    15.11.2001 05:19:18
    187392
    Prg
    CL_GUI_CFW====================
    18.12.2004 13:28:20
    195584
    Typ
    TOLE
    29.07.1998 19:56:01
    2048
    Prg
    SAPLSGOSHIST
    17.09.2006 08:53:33
    56320
    Prg
    SAPFSGOS
    08.11.2003 23:57:36
    13312
    Typ
    SGOSHIST
    14.10.1999 22:09:01
    2048
    Prg
    SAPLURFC
    04.01.2000 19:08:13
    14336
    Prg
    CL_GOS_STARTER================
    09.12.1999 13:49:28
    21504
    Prg
    CL_GUI_CONTROL================
    08.11.2003 23:57:31
    117760
    Prg
    CL_GUI_TOOLBAR================
    15.11.2001 05:19:18
    72704
    Prg
    CL_GUI_GOS_CONTAINER==========
    01.02.2000 10:16:37
    38912
    Typ
    CFW_LINK
    01.12.1999 12:16:48
    2048
    Prg
    CL_GUI_CONTAINER==============
    15.11.2001 05:19:18
    58368
    Prg
    SAPLCNTH
    08.11.2003 23:56:48
    26624
    Prg
    SAPLSCONTROLINFO
    04.01.2000 19:06:52
    13312
    Prg
    SAPLSCONTROLSTATUSCHECK
    04.01.2000 19:06:52
    10240
    Typ
    USR05
    09.07.1997 23:46:52
    1024
    Typ
    CNTLWARN
    25.01.1999 13:09:44
    2048
    Prg
    SAPLICON
    17.09.2006 08:39:01
    25600
    Prg
    %_CICON
    14.08.2000 15:39:36
    55296
    Typ
    JSTO
    27.08.1994 20:32:55
    2048
    Typ
    JEST
    27.08.1994 20:32:50
    2048
    Prg
    SAPLAIEV
    15.11.2001 05:18:17
    14336
    Prg
    CL_OS_TRANSACTION_END_NOTIFIER
    18.12.2004 13:21:30
    8192
    Typ
    LFA1
    13.07.2002 01:08:16
    12288
    Prg
    SAPLCPDB
    17.09.2006 09:17:36
    113664
    Typ
    PLKO
    15.01.1999 22:26:42
    9216
    Prg
    SAPLCCPR
    17.09.2006 09:09:14
    231424
    Typ
    TCC08
    17.03.1999 16:30:21
    4096
    Typ
    AEEF
    13.02.2005 06:49:14
    3072
    Typ
    TCC10
    23.04.1998 14:45:07
    2048
    Typ
    TCCET
    28.08.1997 09:33:24
    1024
    Typ
    TCCEP
    20.08.1998 11:28:15
    2048
    Typ
    TCCER
    10.11.1998 05:49:03
    2048
    Typ
    TCCETT
    14.02.1998 12:45:20
    1024
    Typ
    TCCEPT
    14.02.1998 12:45:07
    1024
    Typ
    TCCERT
    17.03.1999 16:24:38
    2048
    Typ
    TCCS01
    27.08.1999 18:28:00
    1024
    Prg
    SAPLCCHO
    17.09.2006 09:18:17
    55296
    Prg
    SAPLCPTA
    17.09.2006 09:09:03
    122880
    Prg
    SAPLCQTA
    17.09.2006 09:34:41
    88064
    Typ
    TQ33
    10.07.1997 00:12:25
    2048
    Typ
    TQ30
    15.04.1998 00:38:23
    3072
    Typ
    TQ30T
    14.02.1998 14:11:06
    2048
    Prg
    SAPLCV141
    17.09.2006 09:18:22
    86016
    Typ
    DRAD
    01.12.1999 15:17:34
    3072
    Prg
    SAPLBSVT
    16.08.2000 11:43:43
    18432
    Prg
    SAPLSMSG
    18.12.2004 13:27:29
    108544
    Typ
    TJ05
    30.11.1993 16:45:10
    1024
    Typ
    TJ01
    01.03.1999 13:50:12
    4096
    Typ
    TJ07
    30.11.1993 16:45:13
    1024
    Typ
    TJ06
    30.11.1993 16:45:11
    1024
    Typ
    TJ03
    16.08.2000 11:43:42
    2048
    Prg
    SAPFGUICNTL_CFW
    15.11.2001 05:19:19
    17408
    Prg
    CL_GUI_DOCKING_CONTAINER======
    15.11.2001 05:19:18
    50176
    Prg
    SAPLQBCK
    17.09.2006 09:27:37
    106496
    Typ
    QINF
    09.12.1999 19:04:48
    5120
    Typ
    MTQSS
    23.04.1998 14:51:52
    4096
    Prg
    SAPLMAQM
    17.09.2006 09:35:30
    61440
    Typ
    T001W
    18.11.1998 16:27:15
    1024
    Typ
    T001K
    01.02.2000 14:56:09
    3072
    Prg
    SAPLMG21
    17.09.2006 09:34:30
    159744
    Typ
    MARA
    17.09.2006 09:17:34
    15360
    Prg
    SAPLMG22
    17.09.2006 09:17:36
    115712
    Typ
    MARC
    04.01.2000 18:04:45
    23552
    Typ
    RMQEA
    13.08.1997 12:52:02
    9216
    Typ
    TJ02
    27.03.1996 18:28:28
    1024
    Typ
    TJ02T
    14.02.1998 13:40:18
    2048
    Typ
    TJ04
    30.11.1993 16:45:08
    2048
    Prg
    SAPLKDIC
    04.01.2000 19:06:48
    17408
    Prg
    SAPLSDTO
    04.01.2000 19:06:52
    25600
    Typ
    DD07T
    12.05.1997 16:45:51
    2048
    Prg
    SAPLCSCE
    04.01.2000 19:06:44
    8192
    Typ
    T024E
    10.12.1998 18:01:35
    2048
    Prg
    SAPLSCVU
    17.09.2006 08:50:02
    59392
    Typ
    T006A
    28.08.1997 09:04:18
    2048
    Typ
    OLE_PA
    04.04.1995 16:02:19
    2048
    Typ
    ARFCRDATA
    12.07.2002 21:39:11
    3072
    Typ
    SWCBCONT
    14.02.1998 10:14:45
    2048
    Typ
    OLE_VERBS
    04.04.1995 16:02:20
    1024
    Prg
    SAPLSDSD
    17.09.2006 08:53:36
    437248
    Typ
    DDSHIFACE
    20.08.1998 10:51:59
    2048
    Typ
    DFIES
    15.01.1999 16:49:52
    6144
    Typ
    DDSHFPROP
    20.08.1998 10:51:57
    2048
    Typ
    DDSHSELOPT
    20.08.1998 10:52:01
    2048
    Prg
    SAPLSDNT
    18.12.2004 12:05:44
    188416
    Prg
    SAPLSDIF
    18.12.2004 13:03:59
    256000
    Typ
    T006
    29.07.1998 19:25:31
    3072
    Prg
    SAPLSCV0
    17.09.2006 08:50:22
    99328
    Typ
    TCA01
    10.03.1999 18:31:19
    5120
    Typ
    TCA02
    14.02.1998 12:40:44
    2048
    Typ
    TCA35
    06.07.1998 20:51:04
    2048
    Typ
    QMAT
    27.08.1999 18:14:19
    5120
    Typ
    TQ32
    10.07.1997 00:12:23
    2048
    Prg
    SAPLXQPL
    17.09.2006 09:30:13
    28672
    Typ
    TCA44
    29.07.1998 19:44:06
    2048
    Prg
    SAPLQPAP
    17.09.2006 09:30:13
    295936
    Prg
    SAPMSSY0
    17.09.2006 08:53:44
    69632
    Prg
    SAPLSNR3
    17.09.2006 08:53:36
    48128
    Typ
    TNRO
    18.12.2004 13:02:43
    4096
    Prg
    SAPLQEEV
    17.09.2006 09:27:48
    216064
    Typ
    QAPP
    15.04.1998 00:12:33
    7168
    Typ
    TQSS
    20.01.2000 10:08:08
    3072
    Prg
    SAPLQMCF
    17.09.2006 09:34:35
    46080
    Prg
    SAPLCEI0
    03.12.2006 09:44:54
    1121280
    Prg
    SAPLCUEV
    13.07.2002 02:21:41
    11264
    Typ
    IBINCOM
    01.06.1999 11:56:27
    2048
    Typ
    IBINCONF
    01.06.1999 11:56:27
    2048
    Typ
    IBSTCONF
    01.06.1999 11:56:28
    1024
    Prg
    IF_EX_CEI0_INVLD_POSSIBLE=====
    12.02.2005 20:53:18
    4096
    Prg
    CL_EX_CEI0_INVLD_POSSIBLE=====
    12.02.2005 20:52:40
    10240
    Prg
    CL_EXIT_MASTER================
    01.02.2000 09:29:10
    10240
    Typ
    V_EXT_IMP
    14.10.1999 22:16:55
    2048
    Prg
    SAPLCUCB
    17.09.2006 09:34:59
    199680
    Typ
    TCUIBSPECIAL
    15.11.2001 05:31:05
    1024
    Prg
    CL_CBASE======================
    13.02.2005 07:14:09
    95232
    Typ
    T371G
    29.04.1998 10:42:48
    1024
    Prg
    SAPLIBCO
    13.02.2005 05:49:04
    305152
    Prg
    SAPLIBXX
    13.07.2002 02:21:41
    12288
    Prg
    SAPLIBIBF
    13.02.2005 06:58:29
    177152
    Prg
    SAPLIBINF
    13.02.2005 06:58:30
    452608
    Prg
    CL_IBASE_STRUC================
    13.07.2002 02:21:39
    141312
    Prg
    CL_IBASE_STRUC_BUF============
    13.02.2005 01:44:37
    120832
    Prg
    CL_IBASE_STRUC_STAT===========
    13.07.2002 02:21:39
    9216
    Prg
    CL_IBASE_STRUC_BUF_IBSTREF====
    13.02.2005 01:44:37
    61440
    Typ
    IBINVAL
    14.05.1998 22:39:25
    2048
    Prg
    SAPLIBCU
    13.07.2002 02:21:41
    14336
    Prg
    SAPLIBCUT
    13.07.2002 02:21:41
    14336
    Typ
    T371B
    14.05.1998 22:58:43
    1024
    Prg
    CL_IBASE_SERVICE==============
    13.07.2002 02:21:39
    17408
    Prg
    CL_IBASE_T371D_BUF============
    13.07.2002 02:21:39
    15360
    Typ
    T371D
    27.08.1999 18:19:44
    2048
    Prg
    CL_IBASE_R3_MATERIAL==========
    17.09.2006 09:33:39
    99328
    Typ
    MAKT
    28.08.1997 08:52:19
    2048
    Typ
    ICON
    03.01.1996 15:34:02
    3072
    Prg
    IF_EX_CM_BADI_VERSION=========
    12.07.2002 23:55:25
    4096
    Prg
    CL_EX_CM_BADI_VERSION=========
    12.07.2002 23:54:25
    11264
    Prg
    CL_DEF_IM_CM_BADI_VERSION=====
    12.07.2002 23:54:24
    8192
    Prg
    SAPLASTAT_TRIG
    18.12.2004 12:15:52
    12288
    Typ
    ASTAT_TYP2
    10.11.1998 05:35:18
    1024
    Typ
    ASTAT_TYP1
    30.11.1998 15:54:16
    1024
    Prg
    IF_CM_BASELINE================
    13.02.2005 06:50:14
    40960
    Prg
    IF_IBASE_IBOF_TREE_OBJECT=====
    13.02.2005 05:59:51
    10240
    Prg
    IF_IBASE_INSTALL==============
    13.07.2002 02:21:40
    4096
    Prg
    IF_IBASE_MATERIAL=============
    13.07.2002 02:21:40
    4096
    Prg
    IF_IBASE_OBJECT===============
    13.07.2002 02:21:40
    5120
    Prg
    SAPLBOMA
    01.02.2000 14:54:24
    13312

    Hi Sanjay,
      This dump generally occurs when there are inconsistencies between the name of the fields in the fieldcatalog and the names of the fields in the internal table. Please post ur code.(Assuming that this dump has occured in a Z* program)
    Edited by: Rajesh on Dec 29, 2007 2:40 PM

  • Core Dump in Foccur32() due to Address Misalignment

    Hi,
    I am working on Tuxedo 11.1_RP090 with HP-UX IA64, and after a call to tpcall() there is a core dumped due to address alignment issue. The following is excerpt from gdb backtrace.
    <snip>
    Program terminated with signal 10, Bus error.
    BUS_ADRALN - Invalid address alignment. Please refer to the following link that helps in handling unaligned data: http://docs.hp.com/en/7730/newhelp0610/pragmas.htm#pragma-pack-ex3
    #0  0xc000000000211ab0:0 in _lwp_kill+0x30 ()
       from /usr/lib/hpux64/libpthread.so.1
    (gdb) db
    Undefined command: "db".  Try "help".
    (gdb) bt
    #0  0xc000000000211ab0:0 in _lwp_kill+0x30 ()
       from /usr/lib/hpux64/libpthread.so.1
    #1  0xc000000000178810:0 in pthread_kill+0x9d0 ()
       from /usr/lib/hpux64/libpthread.so.1
    #2  0xc0000000003f80e0:0 in raise+0xe0 () from /usr/lib/hpux64/libc.so.1
    #3  0xc00000001e5a2d80:0 in skgesigOSCrash () at skgesig.c:376
    #4  0xc00000001f666900:0 in kpeDbgSignalHandler () at kpedbg.c:1074
    #5  0xc00000001e5a3220:0 in skgesig_sigactionHandler () at skgesig.c:799
    #6  <signal handler called>
    #7  Foccur32 () at Foccur32.c:87
    #8  0xc00000001498c020:0 in _tmaff_delallflds () at affinity.c:725
    #9  0xc00000001498b570:0 in _tmaff_acall () at affinity.c:117
    #10 0xc00000001478f7a0:0 in _tpacall_internal () at tmacall.c:588
    #11 0xc0000000147a2a30:0 in _tpcall_internal () at tmcall.c:349
    #12 0xc0000000147a0ed0:0 in _tpcall_ () at tmcall.c:157
    #13 0xc0000000147a3790:0 in tpcall () at tmcall.c:474
    #14 0xc000000002a3bc90:2 in inline mtux_flags () at my_app.c:1078
    #15 0xc000000002a3bc80:2 in mtux_sync (l_name=<not available>,
        l_service=<not available>, l_request_buf=<not available>,
        l_request_buf_len=<not available>, l_response_buf=<not available>,
        l_response_buf_len=<not available>, l_flags=<not available>)
        at my_app.c:1215
    </snip>
    In Frame 15, there is a call to tpcall() as follows:-
    tpcall((char *)l_service,
                   l_request_buf,
                   l_request_buf_len,
                   l_response_buf,
                   l_response_buf_len,
                   mtux_flags(l_flags))
    From  there the tuxedo code gets called and Signal 10 is raised in Frame 7, inside Foccur32(). Since we do not have the code for Foccur32.c,
    it is difficult for us to determine which address data structure passed as input parameter to tpcall() is misaligned or is it some misaligned pointer in Foccur32() code.
    It would be helpful, if someone can guide as to which structure needs to be examined for possible misalignment.
    Can someone please let me know what can be done to know whether code causing issue at line no. 87 in Foccut32() comes from the parameters passed to tpcall()?
    I am not sure whether it is due to the parameters we pass or due to some internal data structure used by Foccur32().
    Message was edited by: 642aa413-1410-45b0-8534-b407133fb819

    Hi,
    From a quick look at the code in affinity.c I'm guessing that you have a memory corruption problem.  The fault is occurring while trying to access the Tuxedo META TCM, a header that Tuxedo associates with the request.  If you can create a simple reproducer I would suggest opening a support request and provide the reproducer.
    As always, if this is a new problem, what's changed in your environment or application?  Also what is the environment/configuration of your Tuxedo application?
    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

  • Dump in production system :Incorrect status in pricing

    Hi All,
    We have patched out SRM5.5 server system recently with  15 and  16 patch.
    After the patch we are getting  many dums in production system.
    When i check in the ST22 ,the error syaing that
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_BBP_PD_ABORT', was not caught and
        therefore caused a runtime error.
        The reason for the exception is:
         *Incorrect status in pricing*
    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:
        "UNCAUGHT_EXCEPTION" "CX_BBP_PD_ABORT"
        "SAPLBBP_PDH" or "LBBP_PDHU08"
        "BBP_PD_ABORT"
        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
    and  i have checked the IPC ,it is also active only,.
    We have got his issue all of suddenlly,
    Can any one tell us what could be the issue.
    Regards
    cb

    Hi All,
    thanks a lot for your response ,
      I have done the  Simulation which shows everything is fine  and i have chcked with BBP_CND_CUSTOMIZING_CHECK  t-codes even that is also correct  only .
    we are plannning for rasing the issue with SAP.
    Besides that the system might have activated the BADI simple pricing active (or something like that). This would give trouble as well with the IPC (they can't both be active).
    @Robin which the badi we can check.
    once agina thanks a lot for your replys.
    Regards
    cb

  • Getting Dump in Production system

    Hi,
    we are getting dump in one customise program due to missing include program.
    how to transport this missing program.?
    regards,
    Ramesh

    Hi,
    run tcode SE10 in DEV system.
    click on create -> select workbench request -> enter description of request -> enter
    now double click on request -> click change end enter following
    In first row
    Program ID:    R3TR
    Object Type:  PROG
    Object Name: name of include. press enter
    in second row
    Program ID:    LIMU
    Object Type:  REPS
    Object Name: name of include. press enter
    then  click on release.
    import this request in PRD system.
    regards,
    kaushal

  • Short dump in Production system !!!

    Hi Experts,
        We have getting a short dump for all actions in Production system. Suppose if we use se38 and tried to press display it shows a short dump error. Despite when we tried to use tcodes or using LSMW or try to execute a program or like this all type of actions its throws a short dump error. Dont know what is the reason behind that since the short dump is not the defined the reason for the dumb. Have any of you experts got this type of experience?. Pls give your ideas. Thanks in advance.

    Hello Kavi,
    Contact your basis team. SNAP is a table which holds all ABAP dump. It looks like SNAP table is full and cannot accomodate new entries.
    In any production enviornment, the SNAP entires will be deleted regularly and only dumps for the last 8 days will be available
    Check if any job(SM36 or table tbtcp) is running for this program RSSNAPDL in your production system.
    Thanks

  • SAP Smartform Timeout Dump in Production for the invoice form

    Hi Friends,
    I am working on Invoice Smartform. It is working fine when it is having avg line items. where as in my case one invoice iss having more than 500 line items in production. For this in production it is giving timeout short dump.
    In that invoice i am displaying standard fuctionality of invoice form and at the same tim i am displaying Serial Numbers based on delivery and Open Quantity based on Order. So it will take time for back processing.
    Insted of Back ground processing is there any other possibility to solve this. If not Please give me some steps how to implement this form in background based on conditions (if it is having more than 200 line items then only i need to run in background else foreground)
    Pls give me your valuble inputs.
    Thanks,
    Srinivas.

    Hi Vipin,
    Pls provide more details like SP level , Kernel level etc.
    I can see two probable reasons:
    Incorrect installtion of GUI , pls try reinstalling the GUI and then try
    Kernel upgrade but this solely depends on the current level and defer for further investigation.
    Best Regards
    Umesh

Maybe you are looking for