Runtime Error:MESSAGE_TYPE_X in VA01 tcode

Hi All,
I got VA01 tcode Dump While Entering the Texts, in that dump it is showing use SAP note 158985 ,
By using That note number verifed finally i got one relevent note 1104496. And i applied that but still getting same dump. Can any body help me that please give another relevent note for this issue. The Dump is coming from SAPLOLEA  include LOLEAU02 Function Module AC_SYSTEM_FLUSH.
Thnaks & Regards,
Rajasekhar.

generally with SAPOLEA-errors: apply latest version and patch of SAPGUI. this will solve most of those errors.

Similar Messages

  • Runtime error while executing SE30 Tcode as CREATE_DATA_ILLEGAL_LENGTH

    Hi Guys,
    when I am executing a TCode SE30 I am getting following Runtime error .
    Runtime Errors         CREATE_DATA_ILLEGAL_LENGTH
    Except.                CX_SY_CREATE_DATA_ERROR
    Date and Time          23.07.2010 12:28:30
    Short text
         CREATE DATA: Illegal value for the length of an object of the type "X"
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "CL_ABAP_TRACE_FILE============CP" had to be
          terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_CREATE_DATA_ERROR', was not
          caught in
         procedure "READ_INFO" "(METHOD)", 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:
         A data object of the type "X" with length 0 was to be created using
         CREATE DATA. The value 0 is not within the allowed range.
         Allowed range for the length specification:
         Typ C, N, X: 1 .. 65535
         TYP P:       1 .. 16
    Missing RAISING Clause in Interface
    Please suggest me the solution .

    You have to check that in the object(source code) which you are analysing via SE30 .

  • Runtime error while executing VA01

    Hi All,
    I'm getting ABAP dump while executing VA01. Especially while doing variant configurations. 
    Please have a look into following dump.
    Category               ABAP Programming Error
    Runtime Errors         SYNTAX_ERROR
    ABAP Program           SAPMV45A
    Application Component  SD-SLS
    Date and Time          15.12.2011 00:37:01
         Short text
              Syntax error in program "SAPMV45A ".
         What happened?
              Error in the ABAP Application Program
              The current ABAP program "????????????????????????????????????????" had to be
               terminated because it has
              come across a statement that unfortunately cannot be executed.
              The following syntax error occurred in program "SAPMV45A " in include
               "DI_ESD_SAPMV45A===============E " in
              line 184:
              ""TEXT" has already been declared"
              The include has been created and last changed by:
              Created by: "SAP "
              Last changed by: "SANJAY "
              Error in the ABAP Application Program
              The current ABAP program "????????????????????????????????????????" had to be
               terminated because it has
              come across a statement that unfortunately cannot be executed.
         What can you do?
              Please eliminate the error by performing a syntax check
              (or an extended program check) on the program "SAPMV45A ".
              You can also perform the syntax check from the ABAP Editor.
              If the problem persists, proceed as follows:
              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
              The following syntax error was found in the program SAPMV45A :
              ""TEXT" has already been declared"
         How to correct the error
              Probably the only way to eliminate the error is to correct the program.
              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..... 702
              SAP Basis Level. 0003
              Application server... "SANDERP"
              Network address...... "172.16.1.12"
              Operating system..... "Windows NT"
              Release.............. "6.0"
              Hardware type........ "4x AMD64 Level"
              Character length.... 16 Bits
              Pointer length....... 64 Bits
              Work process number.. 3
              Shortdump setting.... "full"
              Database server... "SANDERP"
              Database type..... "DB6"
              Database name..... "OLS"
              Database user ID.. "SAPOLS"
    Thanks in Advance,
    Uday

    Hi
    there is a syntax error in the user exit SAPMV45A created for VA01. Last change was done by sanjay.
    Request your abap team to correct the syntax to resolve the issue.
    Hope this is useful.
    Regards,
    Deepak Kori

  • ABAP Runtime error MESSAGE_TYPE_X in process chain

    in our daily load process chain  we have a level where datas are getting loaded in to a cube from 4 dso thru dtp. in this level the DTP fails approximately twice in a week. the DTP is shown in red in the log view. when  we check the message its showin MESSAGE_TYPE_X ABAP runtime error.
    if we give repeat it runs sucessfully and the following process are going well.
    do u ppl have any ideas abt this.

    Hi,
    This failure would happen for many reasons, like,
    Source system connection failure
    Short dump.
    System overload
    Non availability od work processes as a reasonthe load would have been timed out.
    Locked due to another load.
    That is the reason as to which the load when repeated is successful, as by then,
    The source connection would have been restored
    there would be free processes available
    The other load would have completed.
    Regards,
    Savitha

  • Runtime Error SYNTAX_ERROR with MIGO tcode

    Hi Gurus,
    I got a new issue now. while executing MIGO tcode getting SYNTAX_ERROR dump, please check below dump details..
    Category               ABAP Programming Error
    Runtime Errors         SYNTAX_ERROR
    ABAP Program           SAPLVBDOCUBATCH_DM
    Application Component  LO-BM
    Date and Time          09.01.2012 16:27:51
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLMIGO" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
        The following syntax error occurred in program "SAPLVBDOCUBATCH_DM " in include
         "LVBDOCUBATCH_DM$39 " in
        line 8:
        ""RL034" must be a flat structure. You cannot use internal tables, stri"
        "ngs, references, or structures as components."
        The include has been created and last changed by:
        Created by: "SAP "
        Last changed by: "SAP "
        Error in the ABAP Application Program
        The current ABAP program "SAPLMIGO" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        The following syntax error was found in the program SAPLVBDOCUBATCH_DM :
        ""RL034" must be a flat structure. You cannot use internal tables, stri"
        "ngs, references, or structures as components."
    i have tried to check syntax of program SAPLVBDOCUBATCH_DM and it is giving error, please help me solve this issue.
    Additional Information:ECC6.0 EHP5(recently upgraded from ECC6.0) nd DB:Oracle 10.2.0.2 OS:windows
    Thanks,
    Venkat

    Hello Team,
    This is Solved..
    As per dump when we go n check table RL034 through SE11 there one Object type is wrong so with Abaper help it got corrected then the problem was solved.
    Thanks all for your time.
    Venkat

  • Runtime Error : CONTROL_NOT_FOUND in VA01 / VA02

    Pls go thru the below runtime error and reply ur comments how to resolve it and how it happened.
    Note: The client user donno when it happened actually and said nothing he did.
    Report outputRuntime Errors CONTROL_NOT_FOUND
    CONTROL variable not found
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLIPW1" had to be terminated because one of the
        statements could not be executed.
    This is probably due to an error in the ABAP program.
    Error analysis
        CONTROL " " was searched but was not found.
        This is due to a data inconsistency of a screen and the program or the
        ABAP statement is incorrect (for example, REFRESH CONTROL ... FROM
        SCREEN with an incorrect Control name).
    User and Transaction
        Client.............. 100
        User................ "ZKL45167"
        Language key........ "E"
        Transaction......... "VA01 "
        Program............. "SAPLIPW1"
        Screen.............. "SAPLIPW1 0200"
        Screen line......... 0
    Information on where terminated
        The termination occurred in the ABAP program "SAPLIPW1" in "SYSTEM-EXIT".
        The main program was "SAPMV45A ".
        The termination occurred in line 0 of the source code of the (Include)
         program " "

    Hi,
    It is probably your SET CURSOR that is causing the issue. Comment it and see if the dump doesn't occur.
    check SAP Note 516970 that gives the solution & below blog may help you
    Check the Below CONTROL_NOT_FOUND in VA01(Short Dump)
    Prabhudas

  • SAP Note Number: 852443 | Runtime Error MESSAGE_TYPE_X in Data Source over HANA Source System

    Hi,
    I am facing an issue for Inconsistency in Delta extraction due to a Init Request Mismatch.
    I found out an SAP Note 852443 for the same and it provided me with a workaround solution for the same.
    But , this Issue is frequently reappearing for the same Data Source and I need to find a permanent fix/solution for the same.
    Kindly help me in this.
    Thanks,
    Vimarsh

    Hi.....
    I have gone through the SAP note......what I have understood I will explain you....
    1) You need to compare the Init request (ex : REQU_44H2K09BTG5799G2JXCORI1O5) in both BW and R/3 side....both should be same......
    In the R/3 side the value of the field : RNR of the table :RSSDLINIT should match with the value of the field : INITRNR of the table ROOSPRMSC in the R/3 side.....
    2) If there are NO entries in the RSSDLINIT table in BW, use transaction RSA7 to delete the delta queue for this DataSource/BW application combination in the source system (OLTP).........this step is very simple.......
    3) But the confusion arrise when value is there in the table RSSDLINIT in the BW side.......then check the same Request number in the table ROOSPRMSF and ROOSPRMSC tables with the INITRNR field.
    If, in the ROOSPRMSF and ROOSPRMSC tables for your DataSource source system combination, there are more entries with different INITRNR numbers...............it means if the value doesn't match or multiple values are there then also same solution ...........i.e...........use transaction RSA7 in an OLTP source system to delete all entries ...............then use the Program : RSSM_OLTP_INIT_DELTA_UPDATE  and then delete all init selections in the 'Scheduler/Init selections in the source system' menu in the InfoPackage.......
    4) But if it is a DataMart datasource that is a Export Dtasource then the solution is different.........starting with 8
    But I don't want to confuse you.........first check whether is is a Export Datasource or not.....
    Regards,
    Debjani.....

  • Runtime Error While in Tcode KES1

    Hello Team,
    We are using ECC6 EhP6.
    I am getting a Runtime error while working with Tcode KES1:
    Short text
              Syntax error in program "SAPL0KEA ".
         What happened?
              Error in the ABAP Application Program
              The current ABAP program "SAPLSVIM" had to be terminated because it has
              come across a statement that unfortunately cannot be executed.
              The following syntax error occurred in program "SAPL0KEA " in include "L0KEAT00
    " in
              line 225:
              "The Dictionary structure or table "*T2580" is either not active or doe"
              "s not exist."
              The include has been created and last changed by:
              Created by: "GAURILAD "
              Last changed by: "SAP* "
              Error in the ABAP Application Program
              The current ABAP program "SAPLSVIM" had to be terminated because it has
              come across a statement that unfortunately cannot be executed.
         Error analysis
              The following syntax error was found in the program SAPL0KEA :
              "The Dictionary structure or table "*T2580" is either not active or doe"
              "s not exist."
         Please help me resolve this issue
    Thanks
    Saheli

    Hi Dnyaneshwar,
       Please execute report RKEAGENV  and regenerate operating concern and check if the issue is resolved.
       If not run report RKEAGENF with your operating concern, type of COPA = 1 (costing based) and flag the 'Refill' option. Regenerate the operating concern.
    If running report RKEAGENV will cause another error concerning   operating concern E_B1,then please follow the steps in KBA note  1514122
    Operating concern should be E_B1 even though you may not be using this operating concern.
    regards
    Waman

  • ABAP RUNTIME ERROR WHILE DOING MIRO

    Runtime Errors                                                       MESSAGE_TYPE_X                              
    Date and Time                                                       23.02.2011                    17:07:24          
    Short dump has not been completely stored (too big)                                                                                     
         Short text                                                                                
                   The current application triggered a termination with a short dump.                                                                      
         What happened?                                                                                
                   The current application program detected a situation which really                                                                      
                   should not occur. Therefore, a termination with a short dump was                                                                      
                   triggered on purpose by the key word MESSAGE (type X).                                                                      
         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                                                                                
                   Short text of error message:                                                                      
                   Error creating the document in Profitability Analysis                                                                      
                   Long text of error message:                                                                      
                    Diagnosis                                                                      
                        An error was found while the system was processing the FI/CO                                                                      
                        document in Profitability Analysis.                                                                      
                    System Response                                                                      
                        The document cannot be processed any further.                                                                      
                    Procedure                                                                      
                        Contact your system administrator.                                                                      
                   Technical information about the message:                                                                      
                   Message class....... "KE"                                                                      
                   Number.............. 476                                                                      
                   Variable 1.......... " "                                                                      
                   Variable 2.......... " "                                                                      
                   Variable 3.......... " "                                                                      
                   Variable 4.......... " "                                                                      
         How to correct the error                                                                                
                   Probably the only way to eliminate the error is to correct the program.                                                                      
                   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:                                                                      
                   MESSAGE_TYPE_X " "                                                                      
                   RK2RF001 or "RKEVRK2R_FIX"                                                                      
                   MOVE_VALUE_FIELDS_FI                                                                      
                   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 701                                                                      
                   Application server... "FPELECCPRD"                                                                      
                   Network address...... "192.168.0.24"                                                                      
                   Operating system..... "Windows NT"                                                                      
                   Release.............. "6.0"                                                                      
                   Hardware type........ "16x AMD64 Level"                                                                      
                   Character length.... 16 Bits                                                                      
                   Pointer length....... 64 Bits                                                                      
                   Work process number.. 1                                                                      
                   Shortdump setting.... "full"                                                                      
                   Database server... "FPELECCPRD\FTP"                                                                      
                   Database type..... "MSSQL"                                                                      
                   Database name..... "FTP"                                                                      
                   Database user ID.. "ftp"                                                                      
                   Terminal.......... "PUNE143"                                                                      
                   Char.set.... "C"                                                                      
                   SAP kernel....... 701                                                                      
                   created (date)... "Feb 24 2009 23:27:20"                                                                      
                   create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"                                                                      
                   Database version. "SQL_Server_8.00 "                                                                      
                   Patch level. 32                                                                      
                   Patch text.. " "                                                                      
                   Database............. "MSSQL 9.00.2047 or higher"                                                                      
                   SAP database version. 701                                                                      
                   Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows                                                                      
                    NT 6.0"                                                                      
                   Memory consumption                                                                      
                   Roll.... 16192                                                                      
                   EM...... 29328880                                                                      
                   Heap.... 0                                                                      
                   Page.... 221184                                                                      
                   MM Used. 20281392                                                                      
                   MM Free. 664288                                                                      
         User and Transaction                                                                                
                   Client.............. 900                                                                      
                   User................ "FABUPLO"                                                                      
                   Language key........ "E"                                                                      
                   Transaction......... "MIRO "                                                                      
                   Transactions ID..... "1C413FE0E2E7F1C88D54E61F1346F073"                                                                      
                   Program............. "RK2RF001"                                                                      
                   Screen.............. "SAPLMR1M 6000"                                                                      
                   Screen line......... 34                                                                      
         Information on where terminated                                                                                
                   Termination occurred in the ABAP program "RK2RF001" - in                                                                      
                    "MOVE_VALUE_FIELDS_FI".                                                                      
                   The main program was "SAPLMR1M ".                                                                      
                   In the source code you have the termination point in line 2749                                                                      
                   of the (Include) program "RKEVRK2R_FIX".

    Hi
    Normally what we understand is we should not have a COPA doc in case of MIRO unless and untill one has got the Purchase Price Variance in the entry  and for the same the OKB9 setting has been made while the GL account either doesnot have cost element for the period or the PA structure is not complete.
    The above can be the probable reason for the dump. I hope if you try to investigate the problem on the above line you will find out the solution to the problem
    regards
    Debashis

  • Runtime error in excise tax

    hi
    i am getting runtime error while doing googs receipt with tax code(without tax not getting error).please see this error.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          27.08.2008 20:32:45
    Short dump has not been completely stored (too big)
    Short text
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    Error analysis
    Short text of error message:
    Balance in transaction currency
    Long text of error message:
    Diagnosis
    A balance has occurred in transaction currency 'INR' with the
    following details:
    Exchange rate '00', amount '             8.00-' and currency key
    'INR'.
    The data in the transaction currency were transferred from the
    calling application.
    System Response
    Your data cannot be processed in FI.
    Procedure
    The error is probably in the calling application.
    Technical information about the message:
    Message class....... "F5"
    Number.............. 702
    Variable 1.......... 00
    Variable 2.......... " 8.00-"
    Variable 3.......... "INR"
    Variable 4.......... " "
    Trigger Location of Runtime Error
    Program                                 SAPLMBWL
    Include                                 LMBWLU21
    Row                                     59
    Module type                             (FUNCTION)
    Module Name                             MB_POST_GOODS_MOVEMENT
    Source Code Extract
    Line
    SourceCde
    29
       when a goods movement for an inbound or outbound delivery is posted
    30
       directly from VL31N/ VL01N, XBLNR is not yet known when we call
    31
       CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
    32
       BKPF as well. There is no other way to forward XBLNR to FI as not
    33
       every document is posted by MB_CREATE -> a new function module in
    34
       MBWL for transferring the information, called by FI, meant to load
    35
       the complete function group for all MBxx postings when this isn't
    36
       required (Performance). Would be the better way to transport the
    37
       information after switching off MBxx in later release.
    38
       corresponding IMPORT ... FROM MEMORY ... can be found in
    39
       AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
    40
    l_mem_id = 'MKPF-XBLNR'.                                   " 641365
    41
    EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
    42
    ENDIF.
    43
    IF xmkpf-xabln IS INITIAL.                               "note 434093
    44
    CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
    45
    ENDIF.                                                   "note 434093
    46
    47
    ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
    48
    49
    ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
    50
    CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
    51
    EXCEPTIONS
    52
    error_message = 4.
    53
    As soon as we have started to put things into UPDATE TASK, we must
    54
    ensure that errors definitely terminate the transaction.
    55
    MESSAGE A is not sufficient because it can be catched from
    56
    external callers which COMMIT WORK afterwards, resulting in
    57
    incomplete updates. Read note 385830 for the full story.
    58
    IF NOT sy-subrc IS INITIAL.
    >>>>>
    MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
    60
    sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    61
        MESSAGE A263.
    62
    ENDIF.
    63
    Optische Archivierung
    64
    Spaete Erfassung mit Barcode
    65
    Redesign of barcode handling -> note 780365
    66
    PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
    67
    xmkpf-mjahr
    68
    barcode.
    69
    70
    MOVE-CORRESPONDING xmkpf TO emkpf.
    71
    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
    72
    EXCEPTIONS
    73
    error_message = 4.
    74
    MOVE-CORRESPONDING xmkpf TO emkpf.
    75
    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
    76
    EXCEPTIONS
    77
    error_message = 4.
    78
    IF NOT sy-subrc IS INITIAL.

    Hi,
    Please check the following notes
    Note 1242773 - Getting short dump when doing GR for combined requisitions
    Note 1047059 - Run time error in migo/Goods receipt
    Regards,
    Jigar

  • Runtime Error - Order Status

    Hi friends,
    Pls check below the runtime error description ,which I'm getting when releasing the Order - PM.
    Pls advise, What happ'd and how to fix it.
    Regards
    Sankar.
    Runtime Errors MESSAGE_TYPE_X
    Date and Time 31.03.2008 13:16:08
    Short text 
    The current application triggered a termination with a short dump. 
    What happened? 
    The current application program detected a situation which really 
    should not occur. Therefore, a termination with a short dump was 
    triggered on purpose by the key word MESSAGE (type X). 
    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 
    Short text of error message: 
    Unable to read RFC destination WORKFLOW_LOCAL_250 
    Long text of error message: 
    Technical information about the message: 
    Message class....... "SWF_RUN" 
    Number.............. 617 
    Variable 1.......... "WORKFLOW_LOCAL_250" 
    Variable 2.......... "RFC_READ_DESTINATION_TYPE" 
    Variable 3.......... "DESTINATION_NOT_EXIST" 
    Variable 4.......... " " 
    How to correct the error 
    Probably the only way to eliminate the error is to correct the program. 
    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: 
    "MESSAGE_TYPE_X" " " 
    "CL_SWF_RUN_WIM_LOCAL==========CP" or "CL_SWF_RUN_WIM_LOCAL==========CM088" 
    "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER" 
    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... "SILDEV" 
    Network address...... "192.168.255.70" 
    Operating system..... "Windows NT" 
    Release.............. "5.2" 
    Hardware type........ "4x IA64 Level 3" 
    Character length.... 16 Bits 
    Pointer length....... 64 Bits 
    Work process number.. 2 
    Shortdump setting.... "full" 
    Database server... "SILDEV" 
    Database type..... "MSSQL" 
    Database name..... "DEV" 
    Database user ID.. "dev" 
    Char.set.... "C" 
    SAP kernel....... 700 
    created (date)... "Mar 3 2008 03:55:37" 
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10" 
    Database version. "SQL_Server_8.00 " 
    Patch level. 150 
    Patch text.. " " 
    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, Windows 
    NT 6.0" 
    Memory consumption 
    Roll.... 16192 
    EM...... 8379680 
    Heap.... 0 
    Page.... 16384 
    MM Used. 4889280 
    MM Free. 3487552 
    User and Transaction 
    Client.............. 250 
    User................ "PM5CHARL" 
    Language Key........ "E" 
    Transaction......... " " 
    Transactions ID..... "49F6FEDCA000F177897B0017A4ABF059" 
    Program............. "CL_SWF_RUN_WIM_LOCAL==========CP" 
    Screen.............. "SAPMSSY1 3004" 
    Screen Line......... 2 
    Information on caller of Remote Function Call (RFC): 
    System.............. "DEV" 
    Database Release.... 700 
    Kernel Release...... 700 
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.) 
    Call Type........... "synchron and transactional (emode 0, imode 0)" 
    Inbound TID.........." " 
    Inbound Queue Name..." " 
    Outbound TID........."C0A8FF46013847F096C00004" 
    Outbound Queue Name.." " 
    Client.............. 250 
    User................ "PM5CHARL" 
    Transaction......... " " 
    Call Program........."SAPLERFC" 
    Function Module..... "ARFC_DEST_SHIP" 
    Call Destination.... "NONE" 
    Source Server....... "SILDEV_DEV_00" 
    Source IP Address... "192.168.255.70" 
    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 "CL_SWF_RUN_WIM_LOCAL==========CP" - 
    in "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER". 
    The main program was "SAPMSSY1 ". 
    In the source code you have the termination point in line 10 
    of the (Include) program "CL_SWF_RUN_WIM_LOCAL==========CM088". 
    Source Code Extract 
    Line  SourceCde 
    1 METHOD if_swf_run_wim_utl_internal~get_system_user . 
    2 DATA: l_excp TYPE REF TO cx_swf_run_wim. 
    3  
    4 TRY. 
    5 IF me->m_int_state-system_user IS INITIAL. 
    6 me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
    7 ENDIF. 
    8 re_user = me->m_int_state-system_user. 
    9 CATCH cx_swf_run_wim INTO l_excp. 
    >>>>> MESSAGE ID l_excp->t100_msg-msgid 
    11 TYPE 'X' 
    12 NUMBER l_excp->t100_msg-msgno 
    13 WITH l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2 
    14 l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4. 
    15 ENDTRY. 
    16  
    17 ENDMETHOD. " 
    Contents of system fields 
    Name  Val. 
    SY-SUBRC 0 
    SY-INDEX 2 
    SY-TABIX 1 
    SY-DBCNT 0 
    SY-FDPOS 1 
    SY-LSIND 0 
    SY-PAGNO 0 
    SY-LINNO 1 
    SY-COLNO 1 
    SY-PFKEY  
    SY-UCOMM  
    SY-TITLE CPIC and RFC Control 
    SY-MSGTY X 
    SY-MSGID SWF_RUN 
    SY-MSGNO 617 
    SY-MSGV1 WORKFLOW_LOCAL_250 
    SY-MSGV2 RFC_READ_DESTINATION_TYPE 
    SY-MSGV3 DESTINATION_NOT_EXIST 
    SY-MSGV4  
    SY-MODNO 0 
    SY-DATUM 20080331 
    SY-UZEIT 131608 
    SY-XPROG SAPMSSY1 
    SY-XFORM XAB_READ 
    Active Calls/Events 
    No. Ty. Program Include Line 
    Name 
    26 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM088 10 
    CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER 
    25 METHOD CL_SWF_UTL_MAIL===============CP CL_SWF_UTL_MAIL===============CM00J 5 
    CL_SWF_UTL_MAIL=>GET_OWNER 
    24 METHOD CL_SWF_UTL_MAIL===============CP CL_SWF_UTL_MAIL===============CM002 37 
    CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND 
    23 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM0IE 38 
    CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL 
    22 METHOD CL_SWF_RUN_WIM_STATE==========CP CL_SWF_RUN_WIM_STATE==========CM021 7 
    CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL 
    21 METHOD CL_SWF_RUN_WIM_STATE==========CP CL_SWF_RUN_WIM_STATE==========CM01V 12 
    CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION 
    20 METHOD CL_SWF_RUN_WIM_STATE_FLOW=====CP CL_SWF_RUN_WIM_STATE_FLOW=====CM004 2 
    CL_SWF_RUN_WIM_STATE_FLOW=>IF_SWF_RUN_WIM_STATE~EXECUTE_STATE_TRANSITION 
    19 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM09A 72 
    CL_SWF_RUN_WIM_LOCAL=>SET_STATUS_INTERNAL 
    18 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM0H3 16 
    CL_SWF_RUN_WIM_LOCAL=>_SET_STATUS 
    17 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM04P 7 
    CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SET_STATUS 
    16 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM011 12 
    CL_SWF_RUN_WIM_EXECUTION_MGR=>SET_WORKITEM_STATUS_ERROR 
    15 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM01A 81 
    CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXCEPTION_RESULT 
    14 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM00R 93 
    CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXECUTION_RESULT 
    13 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM008 144 
    CL_SWF_RUN_WIM_EXECUTION_MGR=>START_EXECUTION 
    12 METHOD CL_SWF_RUN_WORKFLOW_START=====CP CL_SWF_RUN_WORKFLOW_START=====CM016 42 
    CL_SWF_RUN_WORKFLOW_START=>START_WORKITEM 
    11 METHOD CL_SWF_RUN_WORKFLOW_START=====CP CL_SWF_RUN_WORKFLOW_START=====CM002 33 
    CL_SWF_RUN_WORKFLOW_START=>EXECUTE 
    10 FUNCTION SAPLSWW_SRV LSWW_SRVU13 135 
    SWW_WI_CREATE_VIA_EVENT_INTERN 
    9 FUNCTION SAPLSWW_SRV LSWW_SRVU11 64 
    SWW_WI_CREATE_VIA_EVENT 
    8 FORM SAPLSWW_SRV LSWW_SRVU11 1 
    SWW_WI_CREATE_VIA_EVENT 
    7 FORM SAPMSSY1 SAPMSSY1 271 
    XAB_RUN_DRIVER 
    6 FUNCTION SAPLSXAB LSXABU01 9 
    RFC_RUN_XAB_DRIVER 
    5 FUNCTION SAPLERFC LERFCU01 115 
    ARFC_EXECUTE 
    4 FUNCTION SAPLERFC LERFCU02 386 
    ARFC_DEST_SHIP 
    3 FORM SAPLERFC LERFCU02 1 
    ARFC_DEST_SHIP 
    2 FORM SAPMSSY1 SAPMSSY1 85 
    REMOTE_FUNCTION_CALL 
    1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30 
    %_RFC_START 
    Chosen variables 
    Name 
    Val. 
    No. 26 Ty. METHOD 
    Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER 
    RE_USER 
    222222222222 
    000000000000 
    000000000000 
    000000000000 
    L_EXCP 
    B0004000 
    90006000 
    SY-MSGID 
    SWF_RUN 
    55455542222222222222 
    376F25E0000000000000 
    00000000000000000000 
    00000000000000000000 
    L_EXCP->T100_MSG-MSGID 
    SWF_RUN 
    55455542222222222222 
    376F25E0000000000000 
    00000000000000000000 
    00000000000000000000 
    SWFCO_WIM_WI_FORWARD 
    SWW_WI_FORWARD 
    555554544554542222222222222222 
    377F79F6F271240000000000000000 
    000000000000000000000000000000 
    000000000000000000000000000000 
    SY-MSGNO 
    617 
    333 
    617 
    000 
    000 
    L_EXCP->T100_MSG+40(6) 
    617 
    333 
    617 
    000 
    000 
    SY-MSGV1 
    WORKFLOW_LOCAL_250 
    54544445544444533322222222222222222222222222222222 
    7F2B6CF7FCF31CF25000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    L_EXCP->T100_MSG+48(100) 
    WORKFLOW_LOCAL_250 
    54544445544444533322222222222222222222222222222222 
    7F2B6CF7FCF31CF25000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    SY-MSGV2 
    RFC_READ_DESTINATION_TYPE 
    54455444544554445444555542222222222222222222222222 
    263F2514F45349E149FEF49050000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    L_EXCP->T100_MSG+148(100) 
    RFC_READ_DESTINATION_TYPE 
    54455444544554445444555542222222222222222222222222 
    263F2514F45349E149FEF49050000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    SY-MSGV3 
    DESTINATION_NOT_EXIST 
    44554445444544554545522222222222222222222222222222 
    45349E149FEFEF4F5893400000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    L_EXCP->T100_MSG+248(100) 
    DESTINATION_NOT_EXIST 
    44554445444544554545522222222222222222222222222222 
    45349E149FEFEF4F5893400000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    SY-MSGV4 
    22222222222222222222222222222222222222222222222222 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    L_EXCP->T100_MSG+348(100) 
    22222222222222222222222222222222222222222222222222 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    %_DUMMY$$ 
    2222 
    0000 
    0000 
    0000 
    No. 25 Ty. METHOD 
    Name CL_SWF_UTL_MAIL=>GET_OWNER 
    RE_OWNER 
    %_DUMMY$$ 
    2222 
    0000 
    0000 
    0000 
    ME->M_OWNER 
    %_VIASELSCR 
    0 
    4 
    ME 
    A0005000 
    E0001000 
    L_WORKITEM 
    60009000 
    3000C000 
    SY-REPID 
    CL_SWF_UTL_MAIL===============CP 
    4455545554544443333333333333334522222222 
    3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000 
    0000000000000000000000000000000000000000 
    0000000000000000000000000000000000000000 
    No. 24 Ty. METHOD 
    Name CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND 
    EX_SENT_TO_ALL 
    2 
    0 
    0 
    0 
    EX_MAIL_OBJECT 
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SYST-REPID 
    CL_SWF_UTL_MAIL===============CP 
    4455545554544443333333333333334522222222 
    3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000 
    0000000000000000000000000000000000000000 
    0000000000000000000000000000000000000000 
    ME 
    A0005000 
    E0001000 
    OBJECT_HD_CHANGE-ACNAM 
    SWW_WI_DISPLAY_FOR_MAIL 
    555554544554455445544442222222222222222222222222222222 
    377F79F4930C19F6F2FD19C0000000000000000000000000000000 
    000000000000000000000000000000000000000000000000000000 
    000000000000000000000000000000000000000000000000000000 
    OBJPARB 
    Table IT_7581x570 
    \CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJPARB 
    Table reference: 224 
    TABH+ 0(20) = E06D6DEFF9060000000000000000000000000000 
    TABH+ 20(20) = E0000000F6020000010000003A020000FFFFFFFF 
    TABH+ 40(16) = 042A0200600B000010000000C1248401 
    store = 0xE06D6DEFF9060000 
    ext1 = 0x0000000000000000 
    shmId = 0 (0x00000000) 
    id = 224 (0xE0000000) 
    label = 758 (0xF6020000) 
    fill = 1 (0x01000000) 
    leng = 570 (0x3A020000) 
    loop = -1 (0xFFFFFFFF) 
    xtyp = TYPE#000046 
    occu = 16 (0x10000000) 
    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 = 0x80095FEFF9060000 
    pgHook = 0x0000000000000000 
    idxPtr = 0x0000000000000000 
    shmTabhSet = 0x0000000000000000 
    id = 540 (0x1C020000) 
    refCount = 0 (0x00000000) 
    tstRefCount = 0 (0x00000000) 
    lineAdmin = 16 (0x10000000) 
    lineAlloc = 16 (0x10000000) 
    shmVersId = 0 (0x00000000) 
    shmRefCount = 1 (0x01000000) 
    >>>>> 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 
    OBJECT_HD_CHANGE-OBJDES 
    Workflow 405090 set to status ERROR 
    56766667233333327672762776777245545222222222222222 
    7F2B6CF70405090035404F03414530522F2000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    %_FSREG_001 
    OBJCONT 
    Table IT_7609x510 
    \CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJCONT 
    Table reference: 225 
    TABH+ 0(20) = 106F6DEFF9060000000000000000000000000000 
    TABH+ 20(20) = E1000000F802000009000000FE010000FFFFFFFF 
    TABH+ 40(16) = 042A0200300B000010000000C1248401 
    store = 0x106F6DEFF9060000 
    ext1 = 0x0000000000000000 
    shmId = 0 (0x00000000) 
    id = 225 (0xE1000000) 
    label = 760 (0xF8020000) 
    fill = 9 (0x09000000) 
    leng = 510 (0xFE010000) 
    loop = -1 (0xFFFFFFFF) 
    xtyp = TYPE#000045 
    occu = 16 (0x10000000) 
    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 = 0x402D5FEFF9060000 
    pgHook = 0x0000000000000000 
    idxPtr = 0x0000000000000000 
    shmTabhSet = 0x0000000000000000 
    id = 541 (0x1D020000) 
    refCount = 0 (0x00000000) 
    tstRefCount = 0 (0x00000000) 
    lineAdmin = 16 (0x10000000) 
    lineAlloc = 16 (0x10000000) 
    shmVersId = 0 (0x00000000) 
    shmRefCount = 1 (0x01000000) 
    >>>>> 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 
    OWNER 
    222222222222 
    000000000000 
    000000000000 
    000000000000 
    SENDER 
    222222222222 
    000000000000 
    000000000000 
    000000000000 
    SY-SUBRC 
    0 
    0000 
    0000 
    SWFCO_MAIL_ERROR_NOTIFY 
    0002 
    3333 
    0002 
    0000 
    0000 
    OBJECT_HD_CHANGE 
    E ERRORMESSAGEWorkflow 405090 set to status ERROR 00000000000000 F F S
    4222222222245545445544456766667233333327672762776777245545222222222222222233333333333333242425
    50000000000522F2D5331757F2B6CF70405090035404F03414530522F2000000000000000000000000000000060603
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    OBJECT_TYPE 
    RAW 
    545 
    217 
    000 
    000 
    SWFCO_OBJTYPE_BOR 
    BO 
    44 
    2F 
    00 
    00 
    No. 23 Ty. METHOD 
    Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL 
    LT_AGENTS 
    Table IT_7521x28 
    \CLASS=CL_SWF_RUN_WIM_LOCAL\METHOD=IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL\DATA=LT_AGEN
    Table reference: 207 
    TABH+ 0(20) = 806B6DEFF9060000000000000000000000000000 
    TABH+ 20(20) = CF000000F0020000010000001C000000FFFFFFFF 
    TABH+ 40(16) = 04180100E006000010000000C1248401 
    store = 0x806B6DEFF9060000 
    ext1 = 0x0000000000000000 
    shmId = 0 (0x00000000) 
    id = 207 (0xCF000000) 
    label = 752 (0xF0020000) 
    fill = 1 (0x01000000) 
    leng = 28 (0x1C000000) 
    loop = -1 (0xFFFFFFFF) 
    xtyp = TYPE#000022 
    occu = 16 (0x10000000) 
    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 = 0xA0696DEFF9060000 
    pgHook = 0x0000000000000000 
    idxPtr = 0x0000000000000000 
    shmTabhSet = 0x0000000000000000 
    id = 537 (0x19020000) 
    refCount = 1 (0x01000000) 
    tstRefCount = 0 (0x00000000) 
    lineAdmin = 16 (0x10000000) 
    lineAlloc = 16 (0x10000000) 
    shmVersId = 0 (0x00000000) 
    shmRefCount = 2 (0x02000000) 
    >>>>> 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 
    SYST-REPID 
    CL_SWF_RUN_WIM_LOCAL==========CP 
    4455545554554454444433333333334522222222 
    3CF376F25EF79DFCF31CDDDDDDDDDD3000000000 
    0000000000000000000000000000000000000000 
    0000000000000000000000000000000000000000 
    ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD+840(28) 
    WS20000014 
    55333333332222 
    73200000140000 
    00000000000000 
    00000000000000 
    SY-REPID 
    CL_SWF_RUN_WIM_LOCAL==========CP 
    4455545554554454444433333333334522222222 
    3CF376F25EF79DFCF31CDDDDDDDDDD3000000000 
    0000000000000000000000000000000000000000 
    0000000000000000000000000000000000000000 
    FUNCNAME 
    SWW_WI_DISPLAY_FOR_MAIL 
    555554544554455445544442222222 
    377F79F4930C19F6F2FD19C0000000 
    000000000000000000000000000000 
    000000000000000000000000000000 
    SWFCO_WI_REMOTE 
    R 
    5 
    2 
    0 
    0 
    PARAMETER-NAME 
    WI_ID 
    54544 
    79F94 
    00000 
    00000 
    SWFCO_CALLBACK_AGENTS 
    CALLBACKAGENTS 
    54444444454444552222222222222222 
    F31CC213BF175E430000000000000000 
    00000000000000000000000000000000 
    00000000000000000000000000000000 
    PARAMETER-VALUE 
    000000405090 
    333333333333 
    000000405090 
    000000000000 
    000000000000 
    ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD-WI_ID 
    000000405090 
    333333333333 
    000000405090 
    000000000000 
    000000000000 
    PARAMETER 
    807020C0 
    7080A050 
    00000000 
    00100010 
    LS_MAILOBJ 
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

    Hi Sankar,
    Clearly RFC destination WORKFLOW_LOCAL_250 doesnot exist. But please don't create it directly using Sm59.
    Log into client 250 and go to transaction SWU3. Here you will get option for creating RFC destination making use of user WF-BATCH. In case there is workflow expert in your project take his help.
    Once this is done this dump should not come.
    Regards.
    Ruchit.

  • IDoc to File, SM58 shows error, ST22 short dump - Runtime error

    Hi friends,
    I am doing a simple IDoc to file scenario using the EVMSTA01 IDoc. My XI is running on client 100 and I am trying to send the IDoc from the client 200 on the same machine. I have completed the design and configuration steps required and also performed the required steps in Sender client (Sm59, we21 and BD54) and receiver client (Sm59, IDX1 and IDX2).
    When I tried sending the IDoc from WE19, status meesage says that, the IDoc has been successfully sent to the receiver but SM58 shows error "IDOC_ERROR_WORKFLOW_START_R". When I looked in to ST22, there was a short dump with the below message -
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          18.10.2008 23:24:29
    ShrtText
         The current application triggered a termination with a short dump.
    What happened?
         The current application program detected a situation which really
         should not occur. Therefore, a termination with a short dump was
         triggered on purpose by the key word MESSAGE (type X).
    Error analysis
         Short text of error message:
         Unable to read RFC destination WORKFLOW_LOCAL_200
         Technical information about the message:
         Message classe...... "SWF_RUN"
         Number.............. 617
         Variable 1.......... "WORKFLOW_LOCAL_200"
         Variable 2.......... "RFC_READ_DESTINATION_TYPE"
         Variable 3.......... "DESTINATION_NOT_EXIST"
         Variable 4.......... " "
         Variable 3.......... "DESTINATION_NOT_EXIST"
         Variable 4.......... " "
    Trigger Location of Runtime Error
         Program                                 CL_SWF_RUN_WIM_LOCAL==========CP
         Include                                 CL_SWF_RUN_WIM_LOCAL==========CM07Z
         Row                                     10
    Module type                             (METHOD)
    Module Name                             IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
    rce Code Extract
    e  SourceCde
    1 METHOD if_swf_run_wim_utl_internal~get_system_user .
    2   DATA: l_excp TYPE REF TO cx_swf_run_wim.
    3
    4   TRY.
    5       IF me->m_int_state-system_user IS INITIAL.
    6         me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
    7       ENDIF.
    8       re_user = me->m_int_state-system_user.
    9     CATCH cx_swf_run_wim INTO l_excp.
    >>       MESSAGE ID     l_excp->t100_msg-msgid
    11               TYPE   'X'
    12               NUMBER l_excp->t100_msg-msgno
    13               WITH   l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
    14                      l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
    15   ENDTRY.
    16
    17 ENDMETHOD.                    "
    Any help would be appreciated..!!
    PS: Points would be assigned to all the helpful replys without fail

    Hi,
    See check for RFC destination and it is working as per your configuration or not , i mean , it is trying to locate remote server.. , so try to check in sm59, remote login and the respective result is going to your required client or not ??
    Also see the further errors while doing Idoc related scenarios..
    IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
    /people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133 - Idoc’s not reaching XI…. Not posted in the receiver SAP
    idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
    IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
    Regards
    Chilla

  • Runtime error when running Init Infopack or delta infopack

    Dear All,
    I am getting following error when trying to init infopack
    Runtime Errors         MESSAGE_TYPE_X
    Message class....... "RSM"
    Number.............. 000
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    Program                                 SAPLRSS1
    Include                                 LRSS1F11
    Row                                     1,543
    Module type                             (FORM)
    Module Name                             RSM1_CHECK_FOR_DELTAUPD
    And this is happening only with one particular infopack of billing item extractor.
    Please help for the same.
    Regards,
    SS

    Hi,
    Can you just give more explanation on what you are trying to do, like conditions.
    Are doing first time init.
    Reg
    Pra

  • Runtime error in custom container

    hi experts,
    i have two custom containers in one screen.In one container i have tree structure and in another one  text editor . in tree structure i have two nodes if i  click on that nodes cursor should go to text area,
    but the problem is when i was try to click on the  node it's giving runtime error,
    how to rectify this error?
    thanks,
    nag.

    hi experts,
    i have two containers in one screen , in one container i have tree structure and in another one i have text editor. if i click on the node
    of the tree it has to read the text object and placed i the text area
    text editor corresponding to that node.but when i am double clicking on the node it is giving dump.
    Runtime Error: MESSAGE_TYPE_X
    A termination of short dump occurred purpose by the keyword message(type X)
    regards,
    nag.

  • RUNTIME Error - User Status for Order release

    HI Friends,
    Pls go thru the run-time error description,which i'm getting on Order release.Pls reply,.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          31.03.2008 13:16:08
    Short text
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    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
    Short text of error message:
    Unable to read RFC destination WORKFLOW_LOCAL_250
    Long text of error message:
    Technical information about the message:
    Message class....... "SWF_RUN"
    Number.............. 617
    Variable 1.......... "WORKFLOW_LOCAL_250"
    Variable 2.......... "RFC_READ_DESTINATION_TYPE"
    Variable 3.......... "DESTINATION_NOT_EXIST"
    Variable 4.......... " "
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
    "MESSAGE_TYPE_X" " "
    "CL_SWF_RUN_WIM_LOCAL==========CP" or "CL_SWF_RUN_WIM_LOCAL==========CM088"
    "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER"
    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... "SILDEV"
    Network address...... "192.168.255.70"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x IA64 Level 3"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 2
    Shortdump setting.... "full"
    Database server... "SILDEV"
    Database type..... "MSSQL"
    Database name..... "DEV"
    Database user ID.. "dev"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Mar 3 2008 03:55:37"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "SQL_Server_8.00 "
    Patch level. 150
    Patch text.. " "
    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, Windows
    NT 6.0"
    Memory consumption
    Roll.... 16192
    EM...... 8379680
    Heap.... 0
    Page.... 16384
    MM Used. 4889280
    MM Free. 3487552
    User and Transaction
    Client.............. 250
    User................ "PM5CHARL"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "49F6FEDCA000F177897B0017A4ABF059"
    Program............. "CL_SWF_RUN_WIM_LOCAL==========CP"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "DEV"
    Database Release.... 700
    Kernel Release...... 700
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchron and transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........."C0A8FF46013847F096C00004"
    Outbound Queue Name.." "
    Client.............. 250
    User................ "PM5CHARL"
    Transaction......... " "
    Call Program........."SAPLERFC"
    Function Module..... "ARFC_DEST_SHIP"
    Call Destination.... "NONE"
    Source Server....... "SILDEV_DEV_00"
    Source IP Address... "192.168.255.70"
    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 "CL_SWF_RUN_WIM_LOCAL==========CP" -
    in "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 10
    of the (Include) program "CL_SWF_RUN_WIM_LOCAL==========CM088".
    Source Code Extract
    Line
    SourceCde
    1
    METHOD if_swf_run_wim_utl_internal~get_system_user .
    2
    DATA: l_excp TYPE REF TO cx_swf_run_wim.
    3
    4
    TRY.
    5
    IF me->m_int_state-system_user IS INITIAL.
    6
    me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
    7
    ENDIF.
    8
    re_user = me->m_int_state-system_user.
    9
    CATCH cx_swf_run_wim INTO l_excp.
    >>>>>
    MESSAGE ID     l_excp->t100_msg-msgid
    11
    TYPE   'X'
    12
    NUMBER l_excp->t100_msg-msgno
    13
    WITH   l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
    14
    l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
    15
    ENDTRY.
    16
    17
    ENDMETHOD.                    "
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    2
    SY-TABIX
    1
    SY-DBCNT
    0
    SY-FDPOS
    1
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    CPIC and RFC Control
    SY-MSGTY
    X
    SY-MSGID
    SWF_RUN
    SY-MSGNO
    617
    SY-MSGV1
    WORKFLOW_LOCAL_250
    SY-MSGV2
    RFC_READ_DESTINATION_TYPE
    SY-MSGV3
    DESTINATION_NOT_EXIST
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080331
    SY-UZEIT
    131608
    SY-XPROG
    SAPMSSY1
    SY-XFORM
    XAB_READ
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    26 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM088    10
    CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
    25 METHOD       CL_SWF_UTL_MAIL===============CP    CL_SWF_UTL_MAIL===============CM00J     5
    CL_SWF_UTL_MAIL=>GET_OWNER
    24 METHOD       CL_SWF_UTL_MAIL===============CP    CL_SWF_UTL_MAIL===============CM002    37
    CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
    23 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM0IE    38
    CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
    22 METHOD       CL_SWF_RUN_WIM_STATE==========CP    CL_SWF_RUN_WIM_STATE==========CM021     7
    CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL
    21 METHOD       CL_SWF_RUN_WIM_STATE==========CP    CL_SWF_RUN_WIM_STATE==========CM01V    12
    CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION
    20 METHOD       CL_SWF_RUN_WIM_STATE_FLOW=====CP    CL_SWF_RUN_WIM_STATE_FLOW=====CM004     2
    CL_SWF_RUN_WIM_STATE_FLOW=>IF_SWF_RUN_WIM_STATE~EXECUTE_STATE_TRANSITION
    19 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM09A    72
    CL_SWF_RUN_WIM_LOCAL=>SET_STATUS_INTERNAL
    18 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM0H3    16
    CL_SWF_RUN_WIM_LOCAL=>_SET_STATUS
    17 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM04P     7
    CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SET_STATUS
    16 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM011    12
    CL_SWF_RUN_WIM_EXECUTION_MGR=>SET_WORKITEM_STATUS_ERROR
    15 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM01A    81
    CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXCEPTION_RESULT
    14 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM00R    93
    CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXECUTION_RESULT
    13 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM008   144
    CL_SWF_RUN_WIM_EXECUTION_MGR=>START_EXECUTION
    12 METHOD       CL_SWF_RUN_WORKFLOW_START=====CP    CL_SWF_RUN_WORKFLOW_START=====CM016    42
    CL_SWF_RUN_WORKFLOW_START=>START_WORKITEM
    11 METHOD       CL_SWF_RUN_WORKFLOW_START=====CP    CL_SWF_RUN_WORKFLOW_START=====CM002    33
    CL_SWF_RUN_WORKFLOW_START=>EXECUTE
    10 FUNCTION     SAPLSWW_SRV                         LSWW_SRVU13                           135
    SWW_WI_CREATE_VIA_EVENT_INTERN
    9 FUNCTION     SAPLSWW_SRV                         LSWW_SRVU11                            64
    SWW_WI_CREATE_VIA_EVENT
    8 FORM         SAPLSWW_SRV                         LSWW_SRVU11                             1
    SWW_WI_CREATE_VIA_EVENT
    7 FORM         SAPMSSY1                            SAPMSSY1                              271
    XAB_RUN_DRIVER
    6 FUNCTION     SAPLSXAB                            LSXABU01                                9
    RFC_RUN_XAB_DRIVER
    5 FUNCTION     SAPLERFC                            LERFCU01                              115
    ARFC_EXECUTE
    4 FUNCTION     SAPLERFC                            LERFCU02                              386
    ARFC_DEST_SHIP
    3 FORM         SAPLERFC                            LERFCU02                                1
    ARFC_DEST_SHIP
    2 FORM         SAPMSSY1                            SAPMSSY1                               85
    REMOTE_FUNCTION_CALL
    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
    %_RFC_START
    Chosen variables
    Name
    Val.
    No.      26 Ty.          METHOD
    Name  CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
    RE_USER
    222222222222
    000000000000
    000000000000
    000000000000
    L_EXCP
    B0004000
    90006000
    SY-MSGID
    SWF_RUN
    55455542222222222222
    376F25E0000000000000
    00000000000000000000
    00000000000000000000
    L_EXCP->T100_MSG-MSGID
    SWF_RUN
    55455542222222222222
    376F25E0000000000000
    00000000000000000000
    00000000000000000000
    SWFCO_WIM_WI_FORWARD
    SWW_WI_FORWARD
    555554544554542222222222222222
    377F79F6F271240000000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    SY-MSGNO
    617
    333
    617
    000
    000
    L_EXCP->T100_MSG+40(6)
    617
    333
    617
    000
    000
    SY-MSGV1
    WORKFLOW_LOCAL_250
    54544445544444533322222222222222222222222222222222
    7F2B6CF7FCF31CF25000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    L_EXCP->T100_MSG+48(100)
    WORKFLOW_LOCAL_250
    54544445544444533322222222222222222222222222222222
    7F2B6CF7FCF31CF25000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    RFC_READ_DESTINATION_TYPE
    54455444544554445444555542222222222222222222222222
    263F2514F45349E149FEF49050000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    L_EXCP->T100_MSG+148(100)
    RFC_READ_DESTINATION_TYPE
    54455444544554445444555542222222222222222222222222
    263F2514F45349E149FEF49050000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    DESTINATION_NOT_EXIST
    44554445444544554545522222222222222222222222222222
    45349E149FEFEF4F5893400000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    L_EXCP->T100_MSG+248(100)
    DESTINATION_NOT_EXIST
    44554445444544554545522222222222222222222222222222
    45349E149FEFEF4F5893400000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    L_EXCP->T100_MSG+348(100)
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    No.      25 Ty.          METHOD
    Name  CL_SWF_UTL_MAIL=>GET_OWNER
    RE_OWNER
    %_DUMMY$$
    2222
    0000
    0000
    0000
    ME->M_OWNER
    %_VIASELSCR
    0
    4
    ME
    A0005000
    E0001000
    L_WORKITEM
    60009000
    3000C000
    SY-REPID
    CL_SWF_UTL_MAIL===============CP
    4455545554544443333333333333334522222222
    3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    No.      24 Ty.          METHOD
    Name  CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
    EX_SENT_TO_ALL
    2
    0
    0
    0
    EX_MAIL_OBJECT
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SYST-REPID
    CL_SWF_UTL_MAIL===============CP
    4455545554544443333333333333334522222222
    3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    ME
    A0005000
    E0001000
    OBJECT_HD_CHANGE-ACNAM
    SWW_WI_DISPLAY_FOR_MAIL
    555554544554455445544442222222222222222222222222222222
    377F79F4930C19F6F2FD19C0000000000000000000000000000000
    000000000000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000000000000000000
    OBJPARB
    Table IT_758[1x570]
    \CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJPARB
    Table reference: 224
    TABH+  0(20) = E06D6DEFF9060000000000000000000000000000
    TABH+ 20(20) = E0000000F6020000010000003A020000FFFFFFFF
    TABH+ 40(16) = 042A0200600B000010000000C1248401
    store        = 0xE06D6DEFF9060000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 224   (0xE0000000)
    label        = 758   (0xF6020000)
    fill         = 1     (0x01000000)
    leng         = 570   (0x3A020000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000046
    occu         = 16    (0x10000000)
    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         = 0x80095FEFF9060000
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 540   (0x1C020000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 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
    OBJECT_HD_CHANGE-OBJDES
    Workflow 405090 set to status ERROR
    56766667233333327672762776777245545222222222222222
    7F2B6CF70405090035404F03414530522F2000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    %_FSREG_001
    OBJCONT
    Table IT_760[9x510]
    \CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJCONT
    Table reference: 225
    TABH+  0(20) = 106F6DEFF9060000000000000000000000000000
    TABH+ 20(20) = E1000000F802000009000000FE010000FFFFFFFF
    TABH+ 40(16) = 042A0200300B000010000000C1248401
    store        = 0x106F6DEFF9060000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 225   (0xE1000000)
    label        = 760   (0xF8020000)
    fill         = 9     (0x09000000)
    leng         = 510   (0xFE010000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000045
    occu         = 16    (0x10000000)
    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         = 0x402D5FEFF9060000
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 541   (0x1D020000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 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
    OWNER
    222222222222
    000000000000
    000000000000
    000000000000
    SENDER
    222222222222
    000000000000
    000000000000
    000000000000
    SY-SUBRC
    0
    0000
    0000
    SWFCO_MAIL_ERROR_NOTIFY
    0002
    3333
    0002
    0000
    0000
    OBJECT_HD_CHANGE
    E          ERRORMESSAGEWorkflow 405090 set to status ERROR                00000000000000 F F S
    4222222222245545445544456766667233333327672762776777245545222222222222222233333333333333242425
    50000000000522F2D5331757F2B6CF70405090035404F03414530522F2000000000000000000000000000000060603
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    OBJECT_TYPE
    RAW
    545
    217
    000
    000
    SWFCO_OBJTYPE_BOR
    BO
    44
    2F
    00
    00
    No.      23 Ty.          METHOD
    Name  CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
    LT_AGENTS
    Table IT_752[1x28]
    \CLASS=CL_SWF_RUN_WIM_LOCAL\METHOD=IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL\DATA=LT_AGEN
    Table reference: 207
    TABH+  0(20) = 806B6DEFF9060000000000000000000000000000
    TABH+ 20(20) = CF000000F0020000010000001C000000FFFFFFFF
    TABH+ 40(16) = 04180100E006000010000000C1248401
    store        = 0x806B6DEFF9060000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 207   (0xCF000000)
    label        = 752   (0xF0020000)
    fill         = 1     (0x01000000)
    leng         = 28    (0x1C000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000022
    occu         = 16    (0x10000000)
    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         = 0xA0696DEFF9060000
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 537   (0x19020000)
    refCount     = 1     (0x01000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 2     (0x02000000)
    >>>>> 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
    SYST-REPID
    CL_SWF_RUN_WIM_LOCAL==========CP
    4455545554554454444433333333334522222222
    3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD+840(28)
    WS20000014
    55333333332222
    73200000140000
    00000000000000
    00000000000000
    SY-REPID
    CL_SWF_RUN_WIM_LOCAL==========CP
    4455545554554454444433333333334522222222
    3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    FUNCNAME
    SWW_WI_DISPLAY_FOR_MAIL
    555554544554455445544442222222
    377F79F4930C19F6F2FD19C0000000
    000000000000000000000000000000
    000000000000000000000000000000
    SWFCO_WI_REMOTE
    R
    5
    2
    0
    0
    PARAMETER-NAME
    WI_ID
    54544
    79F94
    00000
    00000
    SWFCO_CALLBACK_AGENTS
    CALLBACKAGENTS
    54444444454444552222222222222222
    F31CC213BF175E430000000000000000
    00000000000000000000000000000000
    00000000000000000000000000000000
    PARAMETER-VALUE
    000000405090
    333333333333
    000000405090
    000000000000
    000000000000
    ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD-WI_ID
    000000405090
    333333333333
    000000405090
    000000000000
    000000000000
    PARAMETER
    807020C0
    7080A050
    00000000
    00100010
    LS_MAILOBJ
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ME
    60009000
    3000C000
    SWFCO_WORKITEM_OBJECT
    _WORKITEM
    55454454422222222222222222222222
    F7F2B945D00000000000000000000000
    00000000000000000000000000000000
    00000000000000000000000000000000
    No.      22 Ty.          METHOD
    Name  CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL
    SWFCO_WORKITEM_OBJECT
    _WORKITEM
    55454454422222222222222222222222
    F7F2B945D00000000000000000000000
    00000000000000000000000000000000
    00000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    No.      21 Ty.          METHOD
    Name  CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION
    IM_STATE_ACTIONS
    Table IT_279[30x152]
    \CLASS=CL_SWF_RUN_WIM_STATE_FLOW\DATA=M_STATE_ACTIONS
    Table reference: 112
    TABH+  0(20) = 90CE53EFF9060000B04D6BEFF906000000000000
    TABH+ 20(20) = 70000000170100001E0000009800000090010000
    TABH+ 40(16) = 049A01007004000010000000C9248001
    store        = 0x90CE53EFF9060000
    ext1         = 0xB04D6BEFF9060000
    shmId        = 0     (0x00000000)
    id           = 112   (0x70000000)
    label        = 279   (0x17010000)
    fill         = 30    (0x1E000000)
    leng         = 152   (0x98000000)
    loop         = 400   (0x90010000)
    xtyp         = TYPE#000009
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
    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         = 0xF0C453EFF9060000
    pgHook       = 0xF0CE53EFF9060000
    idxPtr       = 0x50E253EFF9060000
    shmTabhSet   = 0x0000000000000000
    id           = 207   (0xCF000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 48    (0x30000000)
    lineAlloc    = 48    (0x30000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x204C6BEFF9060000
    collHook     = 0x0000000000000000
    ext2         = 0x0000000000000000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    SWFCO_WI_NO_DEADLINE
    0000
    3333
    0000
    0000
    0000
    L_OBJ
    A0005000
    D0002000
    ME
    A0005000
    D0002000
    ME->IF_SWF_RUN_WIM_STATE~NEW_STATUS
    ERROR
    455452222222
    522F20000000
    000000000000
    000000000000
    <%_L003>
    ERROR
    455452222222
    522F20000000
    000000000000
    000000000000
    SY-REPID
    CL_SWF_RUN_WIM_STATE==========CP
    4455545554554455545433333333334522222222
    3CF376F25EF79DF34145DDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    <%_L004>
    F
    4
    6
    0
    0
    <STATE_ACTION>
    FERROR       01DYN_SEND_ERROR_REPAIR_MAIL
    4455452222222334545544454554555454455444422222222222222222222222222222222222
    6522F200000000149EF35E4F522F2F250192FD19C00000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000
    <%_L002>
    <%_L002>-WI_STAT
    SYST-REPID
    CL_SWF_RUN_WIM_STATE==========CP
    4455545554554455545433333333334522222222
    3CF376F25EF79DF34145DDDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    SWFCO_WI_STATUS_WILD_CARD
    222222222222
    A00000000000
    000000000000
    000000000000
    <%_L002>-WI_TYPE
    <STATE_ACTION>-METHOD
    DYN_SEND_ERROR_REPAIR_MAIL
    4545544454554555454455444422222222222222222222222222222222222
    49EF35E4F522F2F250192FD19C00000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000
    %_SPACE
    2
    0
    0
    0
    LV_EXCP
    F0000000
    F0000000
    No.      20 Ty.          METHOD
    Name  CL_SWF_RUN_WIM_STATE_FLOW=>

    Hello,
    Get help from your abaper on this.
    Vinay

Maybe you are looking for

  • Error while running JSP Page on Desktop Client PDA

    Hi Experts, I am trying to run MI Project on my local desktop. But it is not able to start. Browser gives the following error: java.lang.ExceptionInInitializerError      at com.model.CalibModel.getUomList(CalibModel.java:75)      at com.jspjava.Order

  • Sequential dates in new numbers 3.0 does it still do it??

    sequential dates in new numbers 3.0 does it still do it?? Hi Gang, Happy New Year. I am attempting to add sequential dates into my budget planner for the new year. I know the old one could do it. I can do sequential numbers in 3.0, just not able to d

  • Query Tuning Assistance - part 7

    filter("FIN_TRANSACTION"."PAYMENT_NBR" IS NOT NULL) 1271 - access("FIN_TRANSACTION"."TRANSACTION_TYPE"="FIN_TRANSACTION_TYPE"."CODE") 1273 - access("S1_CURRENCY_A"."CURRENCY_CODE"="SA"."CURRENCY_CODE") 1275 - access("A"."CURRENCY_CODE"="S1_CURRENCY".

  • Random volume change on midi track during

    Hey guys! For some reason a random midi track will just all of a sudden increase to max on volume while play back and I haven't got any automation on it at all. I have tried unplugging the midi and in again but still won't solve the problem. Anyone k

  • UCCX 8.0 and QM 8.5 Screen recording not working.

    Dear Networkers, We have UCCX 8.0 with QM 8.5 We're using Network recording mode. Everything seems to be ok ! Audio recording is working, but screen recording stopped working ! I can't find why or how it should work again. In fact, checked the proxy