Delete RFC-Destination 'None' - Urgent

hi all,
I have a problem with the RFC-Destinations. In the Transaction SOLUTION_MANAGER i got the message "RFC-Destination NONE does not exist".
But I have created the Destination.
Then I found the SAP Note 61888.
description:
If the destinations NONE, BACK or SAPGUI are inadvertently deleted, they must be recreated:
NONE   : Type I, no further entries
But I cant recreate this Destination, I got the Message: "Not possible. Internal Connections will be generated".
Can please someone help me. It worked 8 weeks and now I got this failure.
Thx
LM

have a look at this sap note: 181591
"Each time an application server of an R/3 System is restarted, the RFC destinations of type I (internal connection) in this R/3 System are maintained again. The following rules apply:
1. There are always the destinations NONE and BACK which point to the respective application servers themselves."
maybe the restart will take care of it?
read the SAP note please
Regards,
michal

Similar Messages

  • RFC Destination None Error for MIGO

    Hi,
    I am getting RFC Destinatnation NONE error while posting Goods Receipt. GTS service for SD and MM is not active. Error showing for FM GRC01_COST_OBJECT_COST.
    Can any one help in this regard.
    Thanks in advance.
    SP Raj

    Hi,
    Pl find the details below of the error.
    Short text
        RFC destination "NONE" does not exist.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLCK36" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        The 'destination' "NONE" for a Remote Function Call
        is unknown.
        You can display the RFC destinations available in the system using
        the transaction SM59.
    Trigger Location of Runtime Error
        Program                                 SAPLCK36
        Include                                 ISAUTO_CK_SAPLCK36============E
        Row                                     812
        Module type                             (FORM)
        Module Name                             PRICE_STRATEGY_NEW
      806 ************************************************************************
      807 *     DOERNER, GRC, 10/11/1999: Add one new strategy:
      808 * 3b. Create costestimate during goods receipt
      809 ************************************************************************
      810     when 4.
      811       if k_debug_loc is initial.
    >>>>>         call function 'GRC01_COST_OBJECT_COST' destination 'NONE'
      813                 exporting
      814                      im_vbeln     = f_mtcom-vbeln
      815                      im_posnr     = f_mtcom-posnr

  • How to delete RFC destination during runtime

    Hi Experts,
    I need to delete the RFC destination (created via SM59) during runtime. Which API can I use to do so?
    Thanks & Best Regards, Johnney.

    Do delete different type of RFC destination at runtime , you can use these FM on the basis of its type:
    1. To Read Type of RFC Destination use
                    RFC_READ_DESTINATION_TYPE
    2. To Delete RFC Destination
                   RFC_MODIFY_ARFC_PARAMETERS
                   RFC_MODIFY_HTTP_DEST_TO_EXT
                   RFC_MODIFY_HTTP_DEST_TO_R3
                   RFC_MODIFY_L_DESTINATION                - Read Documentation
                   RFC_MODIFY_R3_DESTINATION             - Read Documentation
                   RFC_MODIFY_TCPIP_DESTINATION        - Read Documentation
    Regds.
    Suman

  • SRANA deletes RFC destination 0019990ED9FF1DDF9685086EA3365E75

    Hello,
    While checking in Sm21 logs for PI 7.1 i keep on gettnig message SRANA deletes RFC destination 0019990ED9FF1DDF9685086EA3365E75  everyday, can somebody please suggest  if we can avoid this ?
    Regards,
    Sandeep

    Hello Sandeep
    This error is fixed in note #1293582 SysLog: Termination DYNPRO_SEND_IN_BACKGROUND in background (7.10 SP08). There is also a workaround mentioned in the note, if this is required.
    Regards
    Mark

  • Unable to change RFC destination in IT Performance reporting wizard

    Hi Experts,
    I am setting up IT Performance Reporting in my Solman EHP1 system. In the first page of the PErformance reporting wizard, it asked me for RFC destination from BI to Solman(1st field) and Solman to BI (2nd field). I initially entered an existing RFC destination that we are already using in a separate application that has a user with very-limited authorization. Now, I am trying to change the RFC destination by running the same "Configure IT Performance Reporting" wizard but both fields are already GREYED out.
    I tried deleting the RFC destination previously defined in an attempt to reenable the fields but only the 2nd field was enabled. When I try to continue the setup, it results into a Shortdump because it is still looking for the initially defined RFC dest which is defined in the 1st field that cannot be edited.
    SAP has not yet provided us with a solution.Your help is greatly appreciated.
    Thank you very much.

    You canprovide the RFC destination in DOE administration portal. Goto Configurations link and search for "BACKEND DESTINATION" parameter in "BACKEND CONFIGURATION" link. Here you can provide RFC destination at SWCV level or at Data object level.
    After deleting RFC destination in SM59, it will never take you to backend system.

  • RFC destination definition with non-unicode external program

    Hello All,
    we have one issue with our RFID system connecting to WM system (SWD). 
    For most functions, external RFID server/middleware makes RFC call to SAP system.  Means, from outside system to inside SAP.  This seems to be working fine.
    But in one case, SAP needs to print label to RFID printer.  In this case, SAP is calling external RFID server/middleware using RFC destination.  Means, from inside SAP to outside system.  This is failing.
    We think this has something to do with ECC60 being unicode system, and the RFC destination setup.  We define rfc destination "ZRFID_SSI" in SM59.  We define it same way as in as-is SSI 4.6B production system.  But in SWD ECC60 system, SM59 has more options.  We define as 'non-unicode' because target RFID server/middleware is non-unicode Windows server.  RFC destination is actually working ok.
    To send label to printer, SWD calls function ZFSSIRF202 with remote destination ZRFID_SSI.   Listener on RFID server/middleware will respond to function call.  This also seems to be working.  But then, RFID server/middleware cannot process the data from ZFSSIRF202, log says that data is "0".  (Actually, the first time SWD calls, log says 0 data, the 2nd time there is connection failure, the 3rd time it is 0 data, 4th time connection failure, etc, etc.)
    Compared with production environment, everything is the same, except that SAP is unicode system.  So, our suspicion is, that when ECC60 system sends data, it is encoded somewhat a little different than when SAP 46B system sends data.  I have similar experience with our other interface (XSI), also involving RFC desintion, but XML file exchange.  Here, ECC60 is encoding XML file with UTF-16, but SAP46B was encoding with UTF-8.
    Anyone know how to help ?

    Hi Jeongbae,
    as of NW 7.0 EhP2, it is possible to directly set the code page in SM59.
    In earlier releases, this is not possible.
    In general, SAP systems use the logon language (SY-LANGU)  to determine the code page, if this is available.
    Please check SAP note 788239.
    Please also have a look at SAP note 991572 for possible alternative settings, if SY-LANGU is not available.
    In addition I would recommend to have a look at SAP note 1021459.
    However in order to analyze the problem properly, you need to know the exact short dump text (via rfc trace).
    For XML processing, please read SAP note 1017101. UTF-16 should NOT be used in an XML file !
    Best regards,
    Nils Buerckel
    SAP AG

  • RFC Destination - Unicode / non - Unicode behavior

    Hi All,
    In our current production system the RFC destination from R3 to Xi is non-unicode.We have currently 300 Interfaces running using this RFC destination in production.
    In few upcoming requirements for some 15 Interfaces some special characters will come from R3 to Xi system.In this case we need a unicode RFC Destination.
    I have a query here , can i go ahead and change the existing RFC destination to Unicode or is it suggestible to create a new RFC destination only for these 15 Interfaces?
    Need expert advice on this?
    <<Text removed>>
    Regards,
    RK
    Edited by: Matt on Oct 5, 2011 9:38 AM

    Hello,
    The Non-Unicode Single code page systems are supported by SAP for older applications for historical reasons - unicode was not available when they were released. These systems are restricted to only processing characters from their specific code page. This means their can be restrictions if they need to support language combinations that span multiple code pages - basically it is not possible. In addition some languages are not fully available at all for single code page systems like Thai. In addition the Euro symbol is not available.
    Unicode is the future for all applications - SAP or otherwise. The significance at the moment is where customers who needs to convert to unicode to support additional business requirements like additional languages. Converting a system, although a simple process is not a trivial process in terms of time and resources.
    So u can go ahead and change the existing RFC destination to Unicode .it will not create any prob. for other interfaces which are using non unicode setting.
    Regards
    Monica

  • Unicode Or Non-Unicode for RFC Destination.

    Hi,
    while creating a RFC Destination, what role does a Unicode Setting play.
    Should this  by default always set to Unicode. or does it vary from system to system. Is XI  Uniode compatible or not.
    Regards,
    Sita Rama Raju

    Hi Raju,
    As far as i know, by default, this setting is non-unicode, and that whenever you change the setting to unicode, you need to run a unicode test or something.
    cheers,
    Prashanth

  • Creating RFC Destination For UNICODE system From NON-UNICODE system

    hi
    how can i create RFC Destination For UNICODE system( XI ) From NON-UNICODE (R/3) system.
    thanks and regards
    Mithlesh Kumar Jha

    Hi,
    Check these blogs , Hope u would be getting some idea
    <b>/people/thomas.jung3/blog/2004/06/24/bsp-150-a-developer146s-journal-part-v-xml-for-rfcs
    /people/thomas.jung3/blog/2004/11/15/bsp-150-a-developer146s-journal-part-xiii-developing-abap-webservices
    /people/sap.user72/blog/2004/06/19/how-i-started-with-sap-web-development</b>
    Regards,
    Sridhar Reddy

  • BAPI or RFC function to delete a parked non-po document

    Hello,
    Does anybody know a BAPI or RFC function that can be used to delete a parked non-po (G/L) document? At the moment we delete those parked documents with batch input but we want that everything can run in the background with a RFC only user.
    For parking we will use PRELIMINARY_POSTING_FB01 and for posting BAPI_ACC_DOCUMENT (method "post") but I cannot find anything that allows me to delete a parked invoice. (ECC 6.0)
    Thanks for your help.
    Patric

    Hi,
    Please go through the below OSS note 971193:-
    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=971193
    It provides a program for mass deletion of parked document.
    You can run that program in background with batch user.
    Regards,
    Gaurav

  • RFC destination  ((((URGENT PLZZZZZZZZ)

    Hi Sap Gurus
    I am executing  bd82 by giving my  other client  logical system  that means mm_re
    There It is giving one message
    port could to be created  
    RFC destination MM_se( this is RFC destination name) is not specified for mm_se( logical system name)
    Enter RFC destination restart generation is coming what I have to plz guide me
    Points will be rewarded

    Hi,
    You need to create a port from we21 transaction.
    You need to provide these 3 parameters. 1. Rcvpor 2. rvcprt 3. rcvprn.
    in your case rcvpor is RFC destination name (mm_se)
    port no. means your dev server name (like dev200 etc..)
    port type may be LS(Logical system) in your case.
    if its related to vendor then you can create port under LI. or customer then it is KU. etc..
    Look at this link.
    https://secure.topxml.com/biztalkutilities/walkthroughs/SAP%20Configuration.pdf.
    Thanks,
    Yoga.
    Edited by: Yoga JJ on Feb 4, 2008 1:23 AM

  • Urgent !!!! on RFC destination

    Hello friends,
    In RFC DESTINATION  what is gateway service  . Can we give any arbitary value or can we get it some where else...

    Check the below link and it explianed clearly :
    http://help.sap.com/saphelp_nw04s/helpdata/en/b0/6c52418328db2be10000000a1550b0/content.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/b3/05a63babb49547e10000000a114084/content.htm
    http://www.sapfans.com/sapfans/forum/intface/messages/3857.html
    Thanks
    Seshu

  • Declare rfc destination to receive idoc

    i am trying an example to declare rfc destination to receive idoc.  the directions say to create a new destination of type "L" with the name INTERNAL and desination NONE. When i try to create a new rfc desination with destination NONE is says there is already one there but it is of type "I".  It will not let me change this to type "L" and I cannot delete it.
    Any idea how to do this???
    Also when I create it says give a name of INTERNAL but i see no field which says "name".

    hi,
    u shud create rfc dest tye: R/3 connections...that is type 3.
    refer this:
    R/3 side settings
    1. SM 59 (RFC destinations)
    Create a RFC destination pointing to the XI server. The connection type : R/3 connection. The target host: the XI server.
    2. WE 21 (Ports in IDOC processing)
    Create a transactional port. Give the RFC destination created in this.
    3. BD 54
    Create a logical system.
    4. WE 20 (Partner Profiles)
    a. Create a new partner profile under partner type LS.
    b. Assign the message type in outbound parameters.
    c. Open the message type (Dbl click) and configure the receiver port to the port created.
    XI side settings.
    1. SM59 (RFC destination)
    Configure the RFC destination pointing to the R/3 system.
    2. IDX1 (Port maintenance in IDOC Adapter)
    Create a port and provide the RFC destination.
    [reward if helpful]
    regards,
    latika.

  • Short Dump on BAPI_TRANSACTION_COMMIT with destination NONE

    Hi All
    I am using SAP-PM with Compatible Unit(CU) functionality in ECC6 environment.
    After we release the CU design to Generate order we get SHORT DUMP.
    Any help will be of great help.
    I am pasting the details from the dump file here.
    Please let me know.
    Appretaite your help.
    Thanks
    Meghana
    Runtime Errors         CALL_FUNCTION_REMOTE_ERROR
    Date and Time          27.08.2007 18:01:10
    Short text
    "The current application triggered a termination with a short dump."
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "/***/SAPLCUORDER_N" had to be terminated because it
    has
    come across a statement that unfortunately cannot be executed.
    The error occurred during an RFC call to another system.
    In the target system, a short dump has been written as well.
    More detailed information on the error cause can be found there.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An error occurred when executing a REMOTE FUNCTION CALL.
    It was logged under the name "MESSAGE_TYPE_X"
    on the called page.
    How to correct the error
    Please refer to the notes described in the
    short dump.
    System environment
    SAP-Release 700
    Application server... "MB1ES1005"
    Network address...... "10.191.97.206"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "2x Intel 801586"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 3
    Shortdump setting.... "full"
    Database server... "MB1ES1005"
    Database type..... "ORACLE"
    Database name..... "EC6"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Jul 25 2007 00:57:05"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "OCI_10201_SHARE (10.2.0.1.0) "
    Patch level. 121
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    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.... 8176
    EM...... 14633136
    Heap.... 0
    Page.... 131072
    MM Used. 5005432
    MM Free. 1263944
    User and Transaction
    Client.............. 200
    User................ 10086330
    Language key........ "E"
    Transaction......... "/***/DESIGN "
    Transactions ID..... "409954DC5D77F1C58E2D0013725D3B3B"
    Program............. "/***/SAPLCUORDER_N"
    Screen.............. "/***/SAPLCUORDER_N 2000"
    Screen line......... 34
    Information on where terminated
    Termination occurred in the ABAP program "/***/SAPLCUORDER_N" - in
    "SAVE_DESIGN".
    The main program was "/***/SAPLCUORDER_N ".
    In the source code you have the termination point in line 594
    of the (Include) program "/***/LCUORDER_NF07".
    Source Code Extract
    Line
    SourceCde
    564
    ENDIF .
    565
    ENDLOOP .
    566
    IF l_ret-type = 'E' OR
    567
    l_ret-type = 'A' .
    568
    CLEAR: save_okcode .
    569
    570
    Show Messages
    571
    CALL FUNCTION '/***/N_LOG_ADD_MSG'
    572
    EXPORTING
    573
    i_log_type = 'G'
    574
    TABLES
    575
    t_ret      = t_ret.
    576
    PERFORM log_order_create_show  .
    577
    Show first Message
    578
         MESSAGE ID l_ret-id TYPE l_ret-type NUMBER l_ret-number
    579
         WITH
    580
           l_ret-message_v1 l_ret-message_v2
    581
           l_ret-message_v3 l_ret-message_v4.
    582
    CALL FUNCTION '/***/N_DESIGN_INIT' .
    583
    ELSE .
    584
    IF g_design_mode = con_mode_crea.
    585
    Need to update DMS documents with real design number
    586
    PERFORM document_prepare_002 USING con_desnum_tmp_1
    587
    lv_desnum.
    588
    ENDIF.
    589
    Commit design BAPI's
    590
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
    591
    592
    IF save_okcode = con_order.
    593
    Commit order BAPI's
    >>>>>
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    595
    DESTINATION 'NONE'.
    596
    597
    call of fct. RFC_CONNECTION_CLOSE is important to get a new
    598
    initial roll area with initial internal tables next time
    599
    CALL FUNCTION 'RFC_CONNECTION_CLOSE'
    600
    EXPORTING
    601
    destination          = 'NONE'
    602
    EXCEPTIONS
    603
    destination_not_open = 1
    604
    OTHERS               = 2.
    605
    ENDIF.
    606
    607
    IF lv_desnum IS INITIAL .
    608
    lv_desnum = /***/cudesign-desnum .
    609
    ENDIF .
    610
    SET PARAMETER ID '/***/DESNUM' FIELD lv_desnum .
    611
        Changes saved
    612
    MESSAGE ID '/***/MSG' TYPE 'S' NUMBER '529' WITH lv_desnum .
    613
    ENDIF .
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    2000
    SY-UCOMM
    CU01
    SY-TITLE
    Change Design: 50000109
    SY-MSGTY
    X
    SY-MSGID
    00
    SY-MSGNO
    341
    SY-MSGV1
    MESSAGE_TYPE_X
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20070827
    SY-UZEIT
    180110
    SY-XPROG
    SAPMSSY1
    SY-XFORM
    XAB_READ
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    4 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF07                    594
    SAVE_DESIGN
    3 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF07                   2616
    CHECK_AND_SAVE_F07
    2 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF04                    311
    USER_COMMAND_D2000
    1 MODULE (PAI) /***/SAPLCUORDER_N                  /***/LCUORDER_NI05                     28
    USER_COMMAND_2000
    Chosen variables
    Name
    Val.
    No.       4 Ty.          FORM
    Name  SAVE_DESIGN
    %_DUMMY$$
    2222
    0000
    0000
    0000
    CL_GUI_RESOURCES=>COL_TEXTAREA
    31
    1000
    F000
    G_DESIGN_MODE
    R
    5
    2
    0
    0
    CON_MODE_CREA
    I
    4
    9
    0
    0
    GT_NODE_CUI
    Table[initial]
    SY-REPID
    /***/SAPLCUORDER_N
    2454254544545445542222222222222222222222
    F35DF310C35F2452FE0000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    CON_DESNUM_TMP_1
    TM00000001CY
    543333333345
    4D0000000139
    000000000000
    000000000000
    LV_DESNUM
    222222222222
    000000000000
    000000000000
    000000000000
    SAVE_OKCODE
    CU01
    4533222222222222222222222222222222222222222222222222222222222222222222
    3501000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    CON_ORDER
    CU01
    4533222222222222222222222222222222222222222222222222222222222222222222
    3501000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    SY-XPROG
    SAPMSSY1
    5454555322222222222222222222222222222222
    310D339100000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    CON_DELETE
    LVMS
    4545222222222222222222222222222222222222222222222222222222222222222222
    C6D3000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    No.       3 Ty.          FORM
    Name  CHECK_AND_SAVE_F07
    CL_GUI_ALV_GRID=>MC_MB_VIEW
    &MB_VIEW
    2445544522222222222222222222222222222222222222222222222222222222222222
    6D2F695700000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    GT_OP
    Table IT_303[2x1320]
    PROGRAM=/***/SAPLCUORDER_NDATA=GT_OP
    Table reference: 118
    TABH+  0(20) = 7039FC3C5824DB3C00000000760000002F010000
    TABH+ 20(20) = 0200000028050000FFFFFFFF0400000030140000
    TABH+ 40( 8) = 08000000C1308001
    store        = 0x7039FC3C
    ext1         = 0x5824DB3C
    shmId        = 0     (0x00000000)
    id           = 118   (0x76000000)
    label        = 303   (0x2F010000)
    fill         = 2     (0x02000000)
    leng         = 1320  (0x28050000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000093
    occu         = 8     (0x08000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x2010FC3C
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 234   (0xEA000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 8     (0x08000000)
    lineAlloc    = 8     (0x08000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x60B7153D
    collHook     = 0x00000000
    ext2         = 0x1024DB3C
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xE00FFC3C
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    G_BADI_PROGRAM
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    LOG_ERROR
    2
    0
    0
    0
    CON_BUTT_DELETED
    @11QDelete@
    43355466676422222222222222222222222222222222
    011C145C545000000000000000000000000000000000
    00000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000
    G_CU_EXIT_CU_EXPLODE
    F0000000
    F0000000
    /***/CUDESIGN-OBJNR
    CY00000000000000008835
    4533333333333333333333
    3900000000000000008835
    0000000000000000000000
    0000000000000000000000
    CL_GUI_RESOURCES=>COL_TEXTAREA
    31
    1000
    F000
    G_SEC_COUNT
    0
    0000
    0000
    LV_UPD
    X
    5
    8
    0
    0
    %_SPACE
    2
    0
    0
    0
    GS_ROW_NO
    0.0.0.1.
    0000
    1000
    0000
    0000
    SCREEN
    /***/CUDESIGN-GLTRP
    2454245445444244555222222222222222222222222222222222222222222222222222222222222222222222222222
    F35DF3545397ED7C420000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SY-MSGID
    00
    33222222222222222222
    00000000000000000000
    00000000000000000000
    00000000000000000000
    SWO_%CONTAINER
    000000000
    2222222222222222222222222222222233333333322222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SPACE
    2
    0
    0
    0
    SY-MSGNO
    341
    333
    341
    000
    000
    /***/CVCUI-CUTYP
    2
    0
    0
    0
    SY-MSGV1
    MESSAGE_TYPE_X
    44554445555455222222222222222222222222222222222222
    D533175F4905F8000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    No.       2 Ty.          FORM
    Name  USER_COMMAND_D2000
    /***/CVCUI
    0.0.0.0.0.0.0.1.                                                                         000000
    2220000000022222222222222222222222222222222222222222222222222222222222222222222222223333332222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SYST-REPID
    /***/SAPLCUORDER_N
    2454254544545445542222222222222222222222
    F35DF310C35F2452FE0000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    CON_MODE_COPY
    C
    4
    3
    0
    0
    LT_BAPI_RETURN
    Table IT_1778[2x1088]
    PROGRAM=/***/SAPLCUORDER_NFORM=USER_COMMAND_D2000DATA=LT_BAPI_RETURN
    Table reference: 310
    TABH+  0(20) = 8837083D407E1C3D0000000036010000F2060000
    TABH+ 20(20) = 0200000040040000FFFFFFFF04000000F0170000
    TABH+ 40( 8) = 08000000C1308101
    store        = 0x8837083D
    ext1         = 0x407E1C3D
    shmId        = 0     (0x00000000)
    id           = 310   (0x36010000)
    label        = 1778  (0xF2060000)
    fill         = 2     (0x02000000)
    leng         = 1088  (0x40040000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000113
    occu         = 8     (0x08000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 1
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x50C6073D
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 1534  (0xFE050000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 8     (0x08000000)
    lineAlloc    = 8     (0x08000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0x6067033D
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xE82F063D
    delta_head   = 0000000000000000CF000000000000000400000020180000000000004D00430055004F000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    CON_MODE_ORDE
    O
    4
    F
    0
    0
    TGSBT
    22222222222222222222222222222222222222
    00000000000000000000000000000000000000
    00000000000000000000000000000000000000
    00000000000000000000000000000000000000
    CL_GUI_RESOURCES=>COL_TEXTAREA
    31
    1000
    F000
    LS_NUMBERS-AUFNR_NEW
    000001000677
    333333333333
    000001000677
    000000000000
    000000000000
    T024I
    200UT10100PG for Term & Comp
    33355333335426672567622246672222222222222222
    20054101000706F20452D0603FD00000000000000000
    00000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000
    LS_T399X
    200UT10UM01                  X    INST  30UT01UT01
    3335533543322222222222222222252222445522335533553322222222222222222222222222222222222222222222
    20054105D01000000000000000000800009E3400305401540100000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    CON_VBKZ_U
    U
    5
    5
    0
    0
    /***/CU_ORDER_IO-DISP_FACTOR
    2097152
    0
    0
    LS_DESIGN
    200########000050000109DDCY00000000000000008835PROFILE1  0001UT10UM0100220100MWH001
    333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
    200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
    000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
    /***/CUDESIGN
    200########000050000109DDCY00000000000000008835PROFILE1  0001UT10UM0100220100MWH001
    333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
    200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
    000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
    G_DROP_COUNT
    0
    0000
    0000
    LS_DESIGN-DESNUM
    000050000109
    333333333333
    000050000109
    000000000000
    000000000000
    No.       1 Ty.          MODULE (PAI)
    Name  USER_COMMAND_2000
    GT_SELTAB_INIT
    Table[initial]
    Internal notes
    The termination was triggered in function "RfcExtendedReceive"
    of the SAP kernel, in line 422 of the module
    "//bas/700_REL/src/krn/rfc/abrfcrcv.c#4".
    The internal operation just processed is "FUNC".
    Internal mode was started at 20070827180011.
    Status of connection:
    RFC state: " "
    RFC error text: "RFC_ERROR_SYSTEM_FAILURE"
    CPI-C error text: "The current application triggered a termination with a short
    dump."
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Callstack without Exception:
    App       : disp+work.EXE (pid=26488)
    When      : 8/27/2007 18:1:10.942
    Threads   : 2
    Computer Name       : MB1ES1005
    User Name           : ec6adm
    Number of Processors: 2
    Processor Type: x86 Family 15 Model 4 Stepping 10
    Windows Version     : 5.2 Current Build: 3790
    State Dump for Thread Id 5e10
    eax=000f93c0 ebx=0000042c ecx=00003118 edx=00000000 esi=0000042c edi=00000000
    eip=7c82ed54 esp=056d71f0 ebp=056d7260 iopl=0         nv up ei ng nz ac po cy
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00200297
    function : KiFastSystemCallRet
    7c82ed54 c3               ret
    7c82ed55 8da42400000000   lea     esp,[esp]              ss:056d71f0=7c822124
    7c82ed5c 8d642400         lea     esp,[esp]              ss:62bd5803=00000000
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    056d7260 77e6ba42 0000042c 0001d4c0 00000000 056d7298 ntdll!KiFastSystemCallRet
    056d7274 0109504d 0000042c 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
    056d7298 00582118 00582151 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess  (ntstcdbg.c (501))
    056d729c 00582151 7c38b5c8 7c38b5c8 7c38b5c8 01e9b1b8 disp+work!NTStack  (dptstack.c (1367))
    056d72b8 00582185 7c38b5c8 00000000 008b7ec8 7c38b5c8 disp+work!CTrcStack2  (dptstack.c (352))
    056d72c4 008b7ec8 7c38b5c8 00000000 005f0059 00330030 disp+work!CTrcStack  (dptstack.c (182))
    056d72e8 008bb39f 00711076 056d8018 056d7be8 00200020 disp+work!rabax_CStackSave [abrabax.c (7063)
    056d7b90 009eca8b 020b9e4c 020b9e14 000001a6 5d88acf0 disp+work!ab_rabax  (abrabax.c (1243))
    056d7bcc 009ed19e 00000003 00711076 00000020 00000000 disp+work!rcv_message  (abrfcrcv.c (422))
    056d8068 009ed29d 00000003 00000000 00710c47 056d80c0 disp+work!RfcExtendedReceive [abrfcrcv.c (14
    056d808c 00714873 00000003 00710c47 056d80c0 00711076 disp+work!ab_rfcreceive  (abrfcrcv.c (59))
    056d80e4 0071886b 2694a7c8 2694a7cc 2694a7cc 2694a7cc disp+work!jfunc_get  (abfunc.c (5103))
    056d89f4 007191d0 00000003 000000b4 00000000 05e8b7c0 disp+work!jfunc_nonstandard [abfunc.c (1655)
    056dcfb0 006e3e2d 00000003 3ced8f90 00000000 056dd018 disp+work!ab_jfunc  (abfunc.c (554))
    056dd018 0081cb5e 00000000 3ced8f90 056dd164 3cedb514 disp+work!ab_extri  (abextri.c (552))
    056dd02c 00897dbd 00000000 3cedae46 005bf4cd 3ceda13c disp+work!ab_xevent  (abrunt1.c (281))
    056dd038 005bf4cd 3ceda13c 000000ea 3cedae46 00000000 disp+work!ab_dstep  (abdynpro.c (492))
    056dd164 005c25be 3ced8f90 3ced8f90 056dfc78 00000000 disp+work!dynpmcal  (dymainstp.c (2398))
    056dd178 005c1def 00000001 3ced8f90 00000003 056dfc78 disp+work!dynppai0  (dymainstp.c (1004))
    056dd194 00595e69 3ced8f90 00000001 00000001 00000001 disp+work!dynprctl  (dymainstp.c (360))
    056dfcec 00490e06 00000004 0049d15f 00000004 01dadd00 disp+work!dynpen00  (dymain.c (1628))
    056dfcf4 0049d15f 00000004 01dadd00 00000003 00000002 disp+work!Thdynpen00  (thxxhead.c (4773))
    056dfee0 0049d6d6 00000001 00000000 00000000 00430000 disp+work!TskhLoop  (thxxhead.c (4455))
    056dff00 00421c36 00000000 00000000 7ffde000 056dff60 disp+work!ThStart  (thxxhead.c (1173))
    056dff14 00401080 00000003 05876980 00000001 00000000 disp+work!DpMain  (dpxxdisp.c (1121))
    056dff60 01242970 00000003 05876980 05877a10 01cce000 disp+work!nlsui_main  (thxxanf.c (82))
    056dffc0 77e523e5 00000000 00000000 7ffde000 8967f020 disp+work!wmainCRTStartup  (crtexe.c (395))
    056dfff0 00000000 0124282d 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
    State Dump for Thread Id 61fc
    eax=00000000 ebx=00000103 ecx=0587a700 edx=02714360 esi=00000000 edi=00000000
    eip=7c82ed54 esp=0799fec0 ebp=0799ff04 iopl=0         nv up ei pl zr na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    function : KiFastSystemCallRet
    7c82ed54 c3               ret
    7c82ed55 8da42400000000   lea     esp,[esp]              ss:0799fec0=7c821514
    7c82ed5c 8d642400         lea     esp,[esp]              ss:64e9e4d3=00000000
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    0799ff04 0119030a 000006e0 00000000 00000000 0587a798 ntdll!KiFastSystemCallRet
    0799ff84 7c349565 00000000 00000000 00000000 0587a700 disp+work!SigIMsgFunc  (signt.c (610))
    0799ffb8 77e6608b 0587a700 00000000 00000000 0587a700 MSVCR71!endthreadex
    0799ffec 00000000 7c3494f6 0587a700 00000000 00000000 kernel32!GetModuleFileNameA
    List of ABAP programs affected
    Index
    Typ
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    /***/SAPLCUORDER_N
    0
    10.08.2007
    10:12:44
    541696
    E
    1
    Typ
    /***/CUDESIGN
    0
    10.08.2007
    10:05:19
    7168
    2
    Typ
    /***/CU_ORDER_IO
    0
    10.08.2007
    09:53:38
    4096
    3
    Typ
    /***/DESTYPE
    0
    10.08.2007
    10:05:21
    2048
    4
    Typ
    /***/PRF_ORD
    0
    10.08.2007
    10:05:21
    4096
    5
    Prg
    SAPMSSYD
    0
    04.04.2007
    10:28:36
    21504
    E
    6
    Prg
    SAPFSYSCALLS
    0
    09.09.2004
    14:18:32
    8192
    E
    7
    Typ
    /***/G_CUST
    0
    10.08.2007
    09:53:39
    3072
    8
    Prg
    /***/SAPLTABLES
    8
    10.08.2007
    10:13:00
    19456
    E
    9
    Typ
    /***/G_CHAR
    0
    10.08.2007
    10:05:21
    3072
    10
    Prg
    SAPLCTCE
    10
    09.09.2004
    14:18:34
    9216
    E
    11
    Typ
    CABN
    0
    18.09.2001
    10:02:26
    12288
    12
    Prg
    SAPLICON
    12
    04.04.2007
    10:10:28
    27648
    E
    13
    Prg
    %_CICON
    12
    07.02.2006
    10:40:00
    104448
    E
    14
    Typ
    ICONT
    0
    04.04.2007
    10:10:08
    2048
    15
    Typ
    NRIV
    0
    02.04.1998
    08:14:54
    3072
    16
    Prg
    SAPLBSVA
    16
    04.04.2007
    14:47:00
    296960
    E
    17
    Typ
    /***/CU_ORDER_S_OP_N
    0
    10.08.2007
    09:53:39
    14336
    18
    Prg
    CL_GUI_CONTROL================CP
    18
    28.02.2005
    21:03:09
    112640
    E
    19
    Prg
    %_CCNTL
    18
    18.02.2005
    14:15:08
    15360
    E
    20
    Typ
    OBJ_RECORD
    0
    14.02.1998
    08:30:43
    2048
    21
    Prg
    CL_GUI_OBJECT=================CP
    21
    05.07.2005
    13:10:15
    375808
    E
    22
    Prg
    CL_GUI_CFW====================CP
    22
    28.02.2005
    21:03:09
    172032
    E
    23
    Prg
    CL_GUI_PROPS_CONSUMER=========CP
    23
    18.02.2005
    14:15:08
    30720
    E
    24
    Prg
    SAPLTHFB
    24
    04.04.2007
    13:24:38
    390144
    E
    25
    Typ
    EUDB
    0
    06.11.2003
    20:28:08
    8192
    26
    Prg
    SAPLSFES
    26
    08.08.2007
    16:46:17
    259072
    E
    27
    Prg
    SAPLSPLUGIN
    27
    09.09.2004
    14:18:36
    8192
    E
    28
    Prg
    SAPLSTTM

    Yes even i find it strange. But there is no syntax error and the fact is that it was working 2 days back.  Suddenly it has started giving us this dump.
    The code is as follows.
    Commit design BAPI's
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
          IF save_okcode = con_order.
    Commit order BAPI's
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
              DESTINATION 'NONE'.
    Here con_order is CU01.
    Please let me know if anybody has faced this problem earlier.
    Thanks in Advance
    Meghana

  • How to create a RFC destination for extracting data to HANA

    Hello All,
    Could someone help me in providing a document or note on how to create a RFC destination for extracting data from SAP data source to HANA using SAP LT replication server ?
    I am able to create a data base connection while transforming data from non SAP data source,but wasnt able to transform data which is from SAP abap tables .

    Hi Venkatesh,
    In SM59 t.code we create RFC destinations.
    Go thru the video link for creating RFC destinations step by step
    How to setup a trusted RFC connection between SAP systems: a step-by-step guide - YouTube

Maybe you are looking for

  • Podcasts and syncing with iTunes 6.0

    So I just hooked up my iPod with iTunes 6.0 for the first time. After changing the drive letter (don't know why I needed to do that), it seemed to sync fine. Except that it started uploading 188 old podcasts that I've played (Parts of audiobooks). Th

  • Adding attachment to SharePoint Document Library- Is it possible?

    I would like to know if it possible to attach a file to a document library items like one would to a List item. I have read some postings on this very issue but most are a couple years old.  Would like to know if updated technology has possibly solve

  • Why can't i download apps

    Everytime I try to download an app, I get a message "Improve Apple ID Security." Whether I choose to continue or hit Not Now, I can't download the app. What is the problem!?!??!?!

  • What Are the Differences Between String and StringBuffer?

    Both String and StringBuffer are final classes. StringBuffer grows in size dynamically. Could people help to detail other differences between String and StringBuffer?

  • Installing CS6 issues

    Hi everyone. I tried today to install Adobe CS6 to my Macbook 15 inch, Early 2011. Processor is 2 GHZ Intel Core i7 with 16 GB 1333 Mhz DDR3 memory running OSX 10.8.2 software. When I was initialy trying to install the package the computer froze up.