RFC shortdump

Hi,
My scenario is R/3 to Webservice (synchronous scenario).  I have created a
custom function module which is remote enabled.  In RFC Sender Adapter, I
used the same program id which I entered in the RFC destination.  In my
source R3 system, I am able to login remotely using the test connection. 
So the connection between the R/3 and XI system is fine.
I checked the SMGW to check the logged in clients.  The could see the host
and program id in the list.
But when I execute the RFC in the R/3, it's giving a short dump.  It says
The 'destination' "wbser" for a Remote Function Call is unknown.  I also
checked ST22 to analyse the short dump.  It didn't return anything.
I also paste the code here:-
REPORT  Z_WEBSERVICE_GETDATA.
data: lv_data type char10.
CALL FUNCTION 'Z_WEBSERVICE_TEST' destination 'wbser'
EXPORTING
  FROMCODE        = '0001'
  TOCODE          = '0999'
IMPORTING
  DATA       = lv_data.
write : 'Data is : ' , lv_data.
Can anyone suggest how to fix this.
Thanks.
Krishnan

is "wbser" your RFC destination as configured? - case sensitive!
try making a minor change and ensure the cchannel is active and no errors?
all names are the same for the cchannel and the rfc destination's program ID?
did you do a test connection and it was successful?
did you do a cache refresh in XI?
any errors in SM58 on both systems?
any errors in SXMB_MONI and/or the message monitoring?
what is the status and message trail associated with that communication channel in XI RWB?
check all these to narrow down the problem.
sincerely,
--NM

Similar Messages

  • Where used list for RFC function module

    Hi All,
    Is it possible to list where the RFC enabled FM is getting called? I mean in which all system (say RFC present in some Dev system, it might be called somewhere in other systems other than in Dev systems) RFC is getting called.
    Kindly suggest.
    Thanks,
    Ashwini

    Hi Ashwini,
    Is it possible to list where the RFC enabled FM is getting called?
    Yes, there are several ways to do it, if you just need the list of the systems that call your RFC,
    1) look up the technical designs of the interfaces(the ones which use RFCs) that are present in your project.
    2) Enable RFC trace on your system and go through the trace list, you can get help from your BASIS team.
    3) If you have a middleware through which all the interfaces are handled then you can work with the middleware team to identify the source systems which call your RFC.
    4) Add a line in your RFC to update a Z Table on when and from which UID it was called, based on this you can identify the source.
    5) You can add a bug so that your RFC shortdumps, the team from the source team will be sure get in touch with you in this case...just kidding, but a possible solution at the same time.
    Regards,
    Chen

  • Shortdumps because of missing RFC authorization!?

    Hello,
    I developed a report, that calls a function module, stored in many other SAP Systems.
    This report will be called by hundreds of users. But many of these users do not have the appropriate authorizations to call function modules in other systems. If a call is done, SAP throws a shortdump.
    But how can I check first, whether the user has the appropriate authorizations to call RFC modules, without triggering a shortdump?
    thx, holger

    Hi Holger,
    1. I think your worry for checking about authorisation
       for users -
       the triggering point for it is the SHORT DUMP
       which the RFC gives. (if im wrong, let me know)
    2. If the RFC does not give short dump,
       then ur query can be solved.
    3. It a recommended practice by sap to
       call any RFC function
       using EXCEPTIONS.
       2 standard exceptions are ( they might not be available
       in the definiton of FM)
      EXCEPTIONS
        communication_failure = 1  MESSAGE msg_text
        system_failure        = 2  MESSAGE msg_text.
      You can also get the error message.
    4. EG PROGRAM IS BELOW  ( Just copy paste)
    REPORT abc.
    DATA:    msg_text(80) TYPE c.
    CALL FUNCTION 'RFC_PING' DESTINATION 'PRD'
      EXCEPTIONS
        communication_failure = 1  MESSAGE msg_text
        system_failure        = 2  MESSAGE msg_text.
    IF sy-subrc <> 0.
    *----- MESSAGE
    ENDIF.
    5. If u call the rfc in above manner
        short dump will not be there. Morevoer
       u can check the text of error message
       and DIAGNOSE THE ERROR.
    Hope the above helps.
    Regards,
    Amit M.
    Message was edited by: Amit Mittal

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

  • No RFC Destination maintained

    Hi Experts,
    I am doing User Exit for MIGO.
    I have done it successfully.but problem comes when the email is sent to the vendor, MIGO is getting DUMP.
    So, to cross check i have remove the User Exit of MIGO. but to my surprise when i press POST button in MIGO the similiar DUMP comes.
    So wht is the solution for this.
    For your Information DUMP message is:
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          06.12.2007 14:57:55
    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:
    No RFC destination is defined for SAP Global Trade Services
    Long text of error message:
    Technical information about the message:
    Message class....... "/SAPSLL/PLUGINR3"
    Number.............. 002
    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" " "
    "SAPLMBWL" or "LMBWLU21"
    "MB_POST_GOODS_MOVEMENT"
    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... "vngsap1"
    Network address...... "192.168.0.10"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "2x Intel 801586"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "VNGSAP1"
    Database type..... "MSSQL"
    Database name..... "EC6"
    Database user ID.. "ec6"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Mar 20 2007 00:45:21"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "SQL_Server_8.00 "
    Patch level. 102
    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"
    Memory consumption
    Roll.... 8176
    EM...... 21953056
    Heap.... 0
    Page.... 73728
    MM Used. 15443024
    MM Free. 1280936
    User and Transaction
    Client.............. 800
    User................ "VEDHRUV"
    Language key........ "E"
    Transaction......... "MIGO "
    Transactions ID..... " "
    Program............. "SAPLMBWL"
    Screen.............. "SAPLMIGO 0001"
    Screen line......... 18
    Information on where terminated
    Termination occurred in the ABAP program "SAPLMBWL" - in
    "MB_POST_GOODS_MOVEMENT".
    The main program was "SAPLMIGO ".
    In the source code you have the termination point in line 59
    of the (Include) program "LMBWLU21".
    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.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    4
    SY-INDEX
    1
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    MIGO_STATUS
    SY-UCOMM
    OK_POST1
    SY-TITLE
    Goods Receipt Purchase Order 4500017132 - shah
    SY-MSGTY
    X
    SY-MSGID
    /SAPSLL/PLUGINR3
    SY-MSGNO
    002
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20071206
    SY-UZEIT
    145755
    SY-XPROG
    SAPLBPFC
    SY-XFORM
    CONVERSION_EXIT
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    7 FUNCTION     SAPLMBWL                            LMBWLU21                               59
    MB_POST_GOODS_MOVEMENT
    6 METHOD       SAPLMIGO                            LMIGOKG1                              921
    LCL_MIGO_KERNEL=>GOODS_MOVEMENT_POST
    5 METHOD       SAPLMIGO                            LMIGOKD1                              309
    LCL_MIGO_KERNEL=>DOCUMENT_OPERATION
    4 METHOD       SAPLMIGO                            LMIGOKD1                                9
    LCL_MIGO_KERNEL=>DOCUMENT_POST
    3 METHOD       SAPLMIGO                            LMIGOST2                              124
    LCL_MIGO_STATUS=>LIF_MIGO_FRAME~OKCODE_HANDLER
    2 METHOD       SAPLMIGO                            LMIGOFR2                              172
    LCL_MIGO_FRAME=>OKCODE_DISPATCH
    1 MODULE (PAI) SAPLMIGO                            LMIGOPAI                               11
    PAI_OKCODE_DISPATCH
    Chosen variables
    Name
    Val.
    No.       7 Ty.          FUNCTION
    Name  MB_POST_GOODS_MOVEMENT
    XBLNR_SD
    2222
    0000
    0000
    0000
    EMKPF
    000000000000000000          ##
    2222222222333333333333333333222222222200222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    XMSSA[]
    Table IT_3831[0x196]
    FUNCTION-POOL=MBWLDATA=XMSSA[]
    Table reference: 396
    TABH+  0(20) = 0000000088F26C31000000008C010000F70E0000
    TABH+ 20(20) = 00000000C4000000FFFFFFFF04E90400E01B0000
    TABH+ 40( 8) = 08000000C1108001
    store        = 0x00000000
    ext1         = 0x88F26C31
    shmId        = 0     (0x00000000)
    id           = 396   (0x8C010000)
    label        = 3831  (0xF70E0000)
    fill         = 0     (0x00000000)
    leng         = 196   (0xC4000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000134
    occu         = 8     (0x08000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0x40F26C31
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xA0F5EA30
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    RRESWK
    22222222222
    00000000000
    00000000000
    00000000000
    %_SPACE
    2
    0
    0
    0
    L_MEM_ID
    2222222222
    0000000000
    0000000000
    0000000000
    RSJOBINFO
    00000000000000                                  ##
    2222222222222222222222222222222233333333333333222222222222222222222222222222222200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    XMSPR_KEY
    00000000
    222222222222222222222222222222222222233333333
    000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000000000
    SCREEN
    GODYNPRO-DETAIL_TAKE
    4445455424454445544422222222222222222222222222222222222222222222222222222222222222222222222222
    7F49E02FD45419CF41B500000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    IT_RSTRUCT
    Table[initial]
    XMKPF-XABLN
    2222222222
    0000000000
    0000000000
    0000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    SYST-REPID
    SAPLMBWL
    5454445422222222222222222222222222222222
    310CD27C00000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    ODM07M[]
    Table[initial]
    GT_GOCOMP
    000000000000                                             ####              00000000000000
    3333333333332222222222222222222222222222222222222222222220000222222222222223333333333333322222
    000000000000000000000000000000000000000000000000000000000000C000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SY-SUBRC
    4
    0000
    4000
    L_ATPCB
    22222
    00000
    00000
    00000
    XMKPF-MBLNR
    5000011865
    3333333333
    5000011865
    0000000000
    0000000000
    XMKPF-MJAHR
    2007
    3333
    2007
    0000
    0000
    BARCODE
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    T003
    800WE50AMS         X                XX  XXXXXH
    3335433445222222222522222222222222225522555554222222
    80075501D3000000000800000000000000008800888888000000
    0000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000
    KNVV
    00000000                     000
    2222222222222222222222222222222223333333322222222222222222222233322222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    T064B
    2222222222222222222222
    0000000000000000000000
    0000000000000000000000
    0000000000000000000000
    VGMSEG[]
    Table[initial]
    No.       6 Ty.          METHOD
    Name  LCL_MIGO_KERNEL=>GOODS_MOVEMENT_POST
    ES_EMKPF_OLD
    5000011865200700000000000000          ##
    3333333333333333333333333333222222222200222222222222222222222222222222222222222222222222222222
    5000011865200700000000000000000000000010000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    SYST-REPID
    SAPLMIGO
    5454444422222222222222222222222222222222
    310CD97F00000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    LS_EMKPF
    000000000000000000          ##
    2222222222333333333333333333222222222200222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    OREF_TITLEBAR
    |
    | E0001000 |
    | 60009000 |
    | LS_EMKPF-SUBRC |
    | 0 |
    | 0000 |
    | 0000 |
    | C_MOD_ON |
    | 1 |
    | 3 |
    | 1 |
    | 0 |
    | 0 |
    | GOITEM-ERFMG |
    | 0.0.0.0.0.0.1.  |
    | 0001000 |
    | 000000C |
    | LS_EMKPF-MBLNR |
    |  |
    | 2222222222 |
    | 0000000000 |
    | 0000000000 |
    | 0000000000 |
    | SY-XPROG |
    | SAPLBPFC |
    | 5454454422222222222222222222222222222222 |
    | 310C206300000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | SY-REPID |
    | SAPLMIGO |
    | 5454444422222222222222222222222222222222 |
    | 310CD97F00000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | SY-MSGID |
    | /SAPSLL/PLUGINR3 |
    | 25455442545444532222 |
    | F3103CCF0C579E230000 |
    | 00000000000000000000 |
    | 00000000000000000000 |
    | TV_GODEFAULT_TRANSFER-CX |
    | <initial> |
    | <initial> |
    | <initial> |
    | SPACE |
    |  |
    | 2 |
    | 0 |
    | 0 |
    | 0 |
    | SY-MSGNO |
    | 002 |
    | 333 |
    | 002 |
    | 000 |
    | 000 |
    | SY-MSGV1 |
    |  |
    | 22222222222222222222222222222222222222222222222222 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | ES_EMKPF_OLD-MSGV1 |
    |  |
    | 22222222222222222222222222222222222222222222222222 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | SY-MSGV2 |
    |  |
    | 22222222222222222222222222222222222222222222222222 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | SY-MSGV3 |
    |  |
    | 22222222222222222222222222222222222222222222222222 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | SY-MSGV4 |
    |  |
    | 22222222222222222222222222222222222222222222222222 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | GODEFAULT_TV |
    | 101  GR goods receipt |
    | 2222223332245266667276666772222 |
    | 000000101007207FF43025359040000 |
    | 0000000000000000000000000000000 |
    | 0000000000000000000000000000000 |
    | LS_EMKPF-MJAHR |
    | 0000 |
    | 3333 |
    | 0000 |
    | 0000 |
    | 0000 |
    | OREF_TIP |
    |
    D0002000
    90006000
    TV_GOSPLIT-CURRENT_LINE
    <initial>
    <initial>
    <initial>
    No.       5 Ty.          METHOD
    Name  LCL_MIGO_KERNEL=>DOCUMENT_OPERATION
    I_SIMULATE
    2
    0
    0
    0
    I_SIM_VALUES
    2
    0
    0
    0
    I_ERROR_ONLY
    2
    0
    0
    0
    E_OK
    2
    0
    0
    0
    ET_XMSEG
    Table[initial]
    RSJOBINFO
    00000000000000                                  ##
    2222222222222222222222222222222233333333333333222222222222222222222222222222222200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LS_EMKPF
    5000011865200700000000000000          ##
    3333333333333333333333333333222222222200222222222222222222222222222222222222222222222222222222
    5000011865200700000000000000000000000010000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LT_EMSEG
    Table IT_4407[2x744]
    FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_EMSEG
    Table reference: 460
    TABH+  0(20) = F06C0731F83FE73000000000CC01000037110000
    TABH+ 20(20) = 02000000E8020000FFFFFFFF0400000040420100
    TABH+ 40( 8) = 10000000C1308001
    store        = 0xF06C0731
    ext1         = 0xF83FE730
    shmId        = 0     (0x00000000)
    id           = 460   (0xCC010000)
    label        = 4407  (0x37110000)
    fill         = 2     (0x02000000)
    leng         = 744   (0xE8020000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#001704
    occu         = 16    (0x10000000)
    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         = 0xB8902E31
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 3425  (0x610D0000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0xE0D66931
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x00F11C31
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    LT_XMSEG
    Table IT_4408[2x2364]
    FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_XMSEG
    Table reference: 464
    TABH+  0(20) = A0BEF93070D7693100000000D001000038110000
    TABH+ 20(20) = 020000003C090000FFFFFFFF0400000030310100
    TABH+ 40( 8) = 04000000C1308401
    store        = 0xA0BEF930
    ext1         = 0x70D76931
    shmId        = 0     (0x00000000)
    id           = 464   (0xD0010000)
    label        = 4408  (0x38110000)
    fill         = 2     (0x02000000)
    leng         = 2364  (0x3C090000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#001613
    occu         = 4     (0x04000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    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         = 0x28DF3031
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 3511  (0xB70D0000)
    refCount     = 1     (0x01000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 4     (0x04000000)
    lineAlloc    = 4     (0x04000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 2     (0x02000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0x28D76931
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x90F4EA30
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    LT_IMSEG
    Table IT_4396[2x2792]
    FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_IMSEG
    Table reference: 465
    TABH+  0(20) = D0D5693190D7693100000000D10100002C110000
    TABH+ 20(20) = 02000000E80A0000FFFFFFFF04000000E0410100
    TABH+ 40( 8) = 04000000C1308001
    store        = 0xD0D56931
    ext1         = 0x90D76931
    shmId        = 0     (0x00000000)
    id           = 465   (0xD1010000)
    label        = 4396  (0x2C110000)
    fill         = 2     (0x02000000)
    leng         = 2792  (0xE80A0000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#001702
    occu         = 4     (0x04000000)
    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         = 0xE01BC930
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 3413  (0x550D0000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 4     (0x04000000)
    lineAlloc    = 4     (0x04000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0xC8626B31
    collHook     = 0x00000000
    ext2         = 0x80626B31
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xD88C0331
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    LT_CANCEL
    Table[initial]
    ABAP_TRUE
    X
    5
    8
    0
    0
    LCL_MIGO_GLOBALS=>IF_BADI
    |
    | F0000000 |
    | 70008000 |
    | SYST |
    | ######################################T#########œ#################################ÿ##### C#### |
    | 0000000000000000000000000000000000000050000000005000000000000000000000000000109000F00050240000 |
    | 100010000000000000001000100010000000004000C0B0403000000000000000000000000000B00000F00080030400 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000040000000 |
    | 00000000000000000000000000000000000000000000000010000000000000000000000000000000000000D000000C |
    | LS_XMKPF |
    | 80050000118652007WEWEPR20071206200712062007120614575300000000VEDHRUV |
    | 3333333333333333354545533333333333333333333333333333333333333544455522222222222222222222222222 |
    | 8005000011865200775750220071206200712062007120614575300000000654825600000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | ME |
    |
    F0000000
    D0002000
    %_SPACE
    2
    0
    0
    0
    L_NO_ITEMS
    2
    0
    0
    0
    TV_GODEFAULT-CX
    <initial>
    <initial>
    <initial>
    LCL_MIGO_GLOBALS=>CALLER_SYTCODE
    MIGO
    44442222222222222222
    D97F0000000000000000
    00000000000000000000
    00000000000000000000
    LCL_MIGO_GLOBALS=>RETAIL_CONSIGNMENT_ACTIVE
    2
    0
    0
    0
    %_FSREG_001
    No.       4 Ty.          METHOD
    Name  LCL_MIGO_KERNEL=>DOCUMENT_POST
    E_OK
    2
    0
    0
    0
    ME
    |
    | F0000000 |
    | D0002000 |
    | ABAP_FALSE |
    |  |
    | 2 |
    | 0 |
    | 0 |
    | 0 |
    | LCL_MIGO_GLOBALS=>EXTERNAL_CALL_LEAVE_AFTER_POST |
    |  |
    | 2 |
    | 0 |
    | 0 |
    | 0 |
    | %_ARCHIVE |
    |  |
    | 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | No.       3 Ty.          METHOD |
    | Name  LCL_MIGO_STATUS=>LIF_MIGO_FRAME~OKCODE_HANDLER |
    | I_OKCODE |
    | OK_POST1 |
    | 4455455322222222222222222222222222222222222222222222222222222222222222 |
    | FBF0F34100000000000000000000000000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000 |
    | OREF_BADI_LOG |
    |
    D0002000
    5000A000
    %_FSREG_001
    %_PRINT
    000                                                                                0###
    2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LCL_MIGO_GLOBALS=>KERNEL
    |
    | F0000000 |
    | D0002000 |
    | %_VIASELSCR |
    | # |
    | 0 |
    | 4 |
    | OREF_DETAIL_BATCH |
    |
    60009000
    0000F000
    GOSEARCH_PO
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.       2 Ty.          METHOD
    Name  LCL_MIGO_FRAME=>OKCODE_DISPATCH
    I_OKCODE
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    L_MSG_STRING
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    L_OKCODE
    OK_POST1
    4455455322222222222222222222222222222222222222222222222222222222222222
    FBF0F341000000000000000000000000000000000000000000000000000000000

    Hi Dhruv Shah,
           Can you please tell me which user exit you are using for doing that. coz i am in need of that.
    Thanks,
    Ajeeth

  • Problem in Sender RFC adapter

    Hi all,
    Our scenarion is like this
    RFC -> XI -> File
    When we are calling the RFC ( inside a program ) from the client we are getitng a shortdump with the error ...
    'JCO.Server could not find server function 'STOCK_ENQUIRY_OUT'
    any idea where is the exact problem '?
    regards
    Goutam

    Have these basic checks;
    1. Import the RFC and activate the same in XI.
    2. Configuring of RFC adapter - /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    3. Troubleshooting - /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

  • Sender RFC Adapter - Data to be sent from R/3

    I am working on a scenario where I have to send data from an RFC-enabled function module from R/3 to a file server via XI. The entire scenario is asynchronous.
    Sender: RFC Adapter
    Receiver: File Adapter
    I have done all design and the configuration. Both communication channels are working. I have the RFC destination also set up correctly in R/3.
    However, when I run my ABAP program where the RFC-enabled function module is called, I get a shortdump with the message <b>"senderAgreement not found: lookup of binding via CPA-cache failed for".</b>
    Plus: " The error occurred during an RFC call to another system."
    Could someone kidly help?

    Hi,
    Follow these steps :
    1. import the ECC_ Server into ID if not done
    2. Refresh Cache : Tcode  SXI_CACHE
    3. Please check for Sender agreement config
    4. Check out the parameters when  R/3 calls back XI, it passes the SYS-ID and client number and checks the same in the Integration Configuration Under Business System Service-> Adapter Specific Identifiers. The R/3 System ID and the client Number
    Also check out these blogs..
    /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    regards
    Aashish Sinha
    PS : Reward points if helpful

  • XI: RFC -- JDBC communication deep structure

    Hello to all!
    I've got a RFC <--> JDBC szenario. Insert an update statements work fine.
    Now I want to implement a "SELECT"-statement. Therefore the XML-SQL-statements needs a <key>-tags such as:
    <key>
       <col1>value</col1>
       <col2>value</col2>
    </key>
    <key>
      <col2>value</col2>
    </key>
    To represent the key structure in ABAP I did the following steps
    - I created a structure "keyvalue" with fields: column, value (for <col>value</col>),
    - a table type "andkey" with line type "keyvalue",
    -  another table type "orkey" with linetype "andkey"
    I use the table type "orkey" as exporting parameter for the element "selectkey" in my rfc funtion module :
    CALL FUNCTION 'FUBA_JDBC' DESTINATION 'XI'
      EXPORTING
        selectkey         = it_key
      TABLES
        outtab            = it_outtab
      RESPONSE          =
    My problem is now, that the rfc function module creates a shortdump: CALL_FUNCTION_OPEN_ERROR
    Does anybody know a solution? Could I use the table type "orkey" in the rfc?
    Thanks for your suggestions,
    Christian

    Christian,
    This should probably be posted in the abap forum, you can get some help there.
    Regards
    Ravi Raman

  • External RFC logon not possible when auth/rfc_authority_check is set to 9

    Hello,
    we have to logon via RFC to an ECC6 system where auth/rfc_authority_check is set to "9" but SAP gives 'RFCAPI_RFC_SYS_EXCEPTION:RFC_ERROR_SYSTEM_FAILURE' error. If this parameter is set to "1" then logon is ok. I checked Saphelp and Sapnotes but the documentation for this parameter is a little bit unclear. I tried to change authorizations but without success. Does anyone have experience with this topic?
    Many thanks in advance for your help!
    Tamá

    Hello Julius,
    thanks for your answer and sorry for the long delay.
    We have only one instance so I think load balancing cannot be a problem.
    I'd to set authorizations for SRFC but it didn't help. I try to include it here:
    Manually   Authorization Check for RFC Access
    Activity                       Execute
    Name of RFC to be protected    *
    Type of RFC object to be prote Function group
    And another version:
    Manually   Authorization Check for RFC Access
    Activity                       Execute
            +Name of RFC to be protected    RFCPING, RFC_SYSTEM_INFO, SYSTEM_RESET_RFC_SERVER
    Type of RFC object to be prote Function group
    The shortdump created when I try to logon is confusing, because it says that password is incorrect but this is not true. And it says that RFC is sent with invalid user "SAPCPIC".
    I do not really familiar with the RFC authorization concept maybe this caused the problem.
    Many thanks in advance if you can help me!
    Regards
    Tamá

  • FI_GL LOAD GETTING INTO SHORTDUMP  "SAPSQL_ARRAY_INSERT_DUPREC"

    Hi Experts,
        We have FI_GL  DTP load from datasource PSA to  DSO, this was loading sucessfully till 25 of JUNE. From 28 th of June this load is getting into short dump "SAPSQL_ARRAY_INSERT_DUPREC"but surprisingly when i repeat this step the load getting successfull.  please let me know how can i stop this Shortdump in future.
    thanks in advance
    please see the below deatiled shortdump message.
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          07.07.2010 04:15:51
         Short text
              The ABAP/4 Open SQL array insert results in duplicate database records.
         What happened?
              Error in the ABAP Application Program
              The current ABAP program "SAPLSDDO" had to be terminated because it has
              come across a statement that unfortunately cannot be executed.
         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 exception occurred that is explained in detail below.
              The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
               in
              procedure "DD_DTEL_SET_PUT" "(FUNCTION)", 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:
              If you use an ABAP/4 Open SQL array insert to insert a record in
              the database and that record already exists with the same key,
              this results in a termination.
              (With an ABAP/4 Open SQL single record insert in the same error
              situation, processing does not terminate, but SY-SUBRC is set to 4.)
         How to correct the error
              Use an ABAP/4 Open SQL array insert only if you are sure that none of
              the records passed already exists in the database.
              If the error 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:
              "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
              "SAPLSDDO" or "LSDDOU08"
              "DD_DTEL_SET_PUT"
              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.
              The exception must either be prevented, caught within proedure
              "DD_DTEL_SET_PUT" "(FUNCTION)", or its possible occurrence must be declared in
               the
              RAISING clause of the procedure.
              To prevent the exception, note the following:
         System environment
              SAP-Release 701
              Application server... "EUAX418-ZEP"
              Network address...... "10.129.6.97"
              Operating system..... "AIX"
              Release.............. "5.3"
              Hardware type........ "00C13D524C00"
              Character length.... 16 Bits
              Pointer length....... 64 Bits
              Work process number.. 18
              Shortdump setting.... "full"
              Database server... "EUAX418-ZEP"
              Database type..... "DB6"
              Database name..... "BWP"
              Database user ID.. "SAPBWP"
              Terminal.......... " "
              Char.set.... "C"
              SAP kernel....... 701
              created (date)... "Feb 15 2010 21:28:06"
              create on........ "AIX 2 5 00CB5A5B4C00"
              Database version. "DB6_81 "
              Patch level. 81
              Patch text.. " "
              Database............. "DB6 08.02., DB6 09."
              SAP database version. 701
              Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
              Memory consumption
              Roll.... 16192
              EM...... 16759392
              Heap.... 0
              Page.... 24576
              MM Used. 6041768
              MM Free. 2335128
         User and Transaction
              Client.............. 100
              User................ "ALEREMOTE"
              Language key........ "E"
              Transaction......... " "
              Transactions ID..... "4C27AEF624350086E10080000A810661"
              Program............. "SAPLSDDO"
              Screen.............. "SAPMSSY0 1000"
              Screen line......... 6
         Information on where terminated
              Termination occurred in the ABAP program "SAPLSDDO" - in "DD_DTEL_SET_PUT".
              The main program was "RSBATCH_EXECUTE_PROZESS ".
              In the source code you have the termination point in line 54
              of the (Include) program "LSDDOU08".
              The program "SAPLSDDO" was started as a background job.
              Job Name....... "BIDTPR_207115_1"
              Job Initiator.. "ALEREMOTE"
              Job Number..... 04140400
              The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
              procedure "DD_DTEL_SET_PUT" "(FUNCTION)", but it was neither handled locally
               nor declared
              in the RAISING clause of its signature.
              The procedure is in program "SAPLSDDO "; its source code begins in line
              1 of the (Include program "LSDDOU08 ".
                 leng         = 4     (0x00000004)
                 loop         = -1    (0xFFFFFFFF)
                 xtyp         = TYPE#000126
                 occu         = 25    (0x00000019)
                 access       = 1     (ItAccessStandard)
                 idxKind      = 0     (ItIndexNone)
                 uniKind      = 2     (ItUniqueNon)
                 keyKind      = 1     (default)
                 cmpMode      = 0     (cmpAllDynamic)
                 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         = 0x07000000606AC9E8
                 pgHook       = 0x0000000000000000
                 idxPtr       = 0x0000000000000000
                 shmTabhSet   = 0x0000000000000000
                 id           = 2095  (0x0000082F)
                 refCount     = 0     (0x00000000)
                 tstRefCount  = 0     (0x00000000)
                 lineAdmin    = 25    (0x00000019)
                 lineAlloc    = 25    (0x00000019)
                 shmVersId    = 0     (0x00000000)
                 shmRefCount  = 1     (0x00000001)
                 >>>>> 1st level extension part <<<<<
                 regHook      = Not allocated
                 collHook     = Not allocated
                 ext2         = Not allocated
                 >>>>> 2nd level extension part <<<<<
                 tabhBack     = Not allocated
                 delta_head   = Not allocated
                 pb_func      = Not allocated
                 pb_handle    = Not allocated
         I

    Hi,
    This error due to that you are inserting duplicate records into DSO Key fields.
    Check your record in PSA and remove duplicate reocrds from PSA and try to run transformation again or you need to change primary key of your DSO to fit PSA data.
    Thank you,
    Regards,
    Govind.

  • RFC authorizations.

    Situation:
    After replacing old roles on my system that had auth obj. S_RFC with following values
    [ACTVT = 16; RFC_NAME = *; RFC_TYPE = FUGR;]
    in most of them, my system is plagued by RFC_NO_AUTHORITY short-dumps. I'm yet to see any transaction that has profile generator defaults (SU24) maintained for S_RFC object although many have this object as "Checked", and, as far as I know, there is no way to determine what RFC calls the transaction could make ahead of time. As far as I can understand, all these calls are local, e.g. target is "NONE" in the shortdump.
    Question for the experts here:
    What is the most correct way to handle this situation? What am I missing here?
    Feeling a bit lost, here.
    Edited by: Martinsh Shaiters on Jun 1, 2009 6:20 PM

    Please take a look at the note mentioned by Zaheer in Restricting RFC User access
    The checks are config dependent (RZ11 --> auth/rfc_authority_check) but the SM20 logs will record them (and sometimes more) independently of this. This is usefull but can be misleading if you are not aware of your config.
    Internal RFC authority is not checked by default (e.g. destination "NONE") even although the logs might say so. I know that SAP is looking into the SM20 aspect of this "always write a log" but the short-dumps can be more misleading. IMO it is not acceptable to "tollerate" short dumps though...
    See login/isolate_rfc_system_calls and auth/rfc_authority_check for an explanation for the different RFC_TYPE's. You are currently only using FUGR...
    So, which FUGR is it? Is there anything corresponding to them in SM13? (that would be more critical)
    Also, which release / SP / Kernel level / OS are you on?
    If you are interested in more technical details of SM20, with possible consequences for ST22, then see SY-XFORM = 'XAB_READ' called successfully, but what is it?
    Cheers and please give us more details,
    Julius

  • RFC Function module executing in tasks error

    Hi Gurus,
    I have a rfc enabled function module that I am executing in tasks . The first two passes went correct but the third pass gave the shortdump: Communication failure.
    What can be done to correct this .
    A RAISE statement in the program "SAPLYQM_PLANT_REL" raised the exception
    condition "COMMUNICATION_FAILURE".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    >>>>>>CALL FUNCTION 'YQM_SAMPLE_RELEASE_TASKS' starting new task 'FUNC1'
                destination 'NONE'
                 performing set_function1_done on end of task
         EXPORTING
           I_PHYNR      = i_PHYNR
           I_YYPREPDATE = i_YYPREPDATE
           I_REL        = I_REL
         TABLES
           T_RETURN     = t_RETURN.
       wait until functioncall1 = done.
    Thank you .

    Hi,
    the error COMMUNICATION FAILURE occurs if a server is unavailable for  processing of the task or possibly there is no free processes available.
    Check this link.
    It has a good example how to handle teh error.
    [http://saphelp.border-states.com/EN/fa/096e92543b11d1898e0000e8322d00/frameset.htm]
    Regards,
    Ankur Parab

  • RFC failed

    hi,
    RFC has failed, and i ve even checked it,.
    it showed rfc failed;
    if i need to give RFC connection,, how can i go about.. kindly tell give me steps,,,to make RFC working...
    happy
    ashwin

    SM58 to check the RFC Connection.
    Usually thre will be shortdump accompanying TRFC errors. The details of error message can be found in the dump and corrective actions can be taken based on that
    http://help.sap.com/saphelp_nw70/helpdata/en/89/45aad99715462abdf09ec503e151e7/frameset.htm
    Message was edited by:
            Aduri

  • How to find RFCs/BAPIs

    Hi,
      I need to call RFCs/BAPIs from a web application outside SAP for various monitoring things like IDOC Monitoring,Shortdump monitoring etc.
    The following are the things what I need to get using RFCs/BAPIs from SAP.
    Let me know, if anyone have any idea about the RFCs for the below things
    a)     SAP User-Statistic-files (stat-files)
    Target is to get all info who was doing what in the SAP
    b)     Workprocess-Overview
    c)     Server-Overview
    d)     User-Overview (active users / Connected users)
    e)     Addressdata of the users and Companies
    f)     Client List
    g)     Batch Job-Overview
    Stopped Jobs, Runtime of them, user that started the job, Jobname, gui-name, and delay of starting
    h)     Shortdumps
    Shortdump list
    i)     Update check
    Status of the update processes
    j)     Batch input Folder
    Staus and Problems
    k)     IDOC
    Idoc Number and errors
    l)     Syslog Info / Filter
    SM21
    m)     Average Responsetime
    (by day, hour = Moni-files / CCMS) Number of (Dialog-User-Dialogsteps, Dialog-Program-Dialogsteps, Batch-programs, print/Spool-jobs, Update)
    n)     Loging of processes
    o)     Backup status

    Hi
    Use the Tcode BAPI to find the different BApis related to the different functionality
    see the Links
    BAPI
    http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/5e114a4a1611d1894c0000e829fbbd/frameset.htm
    http://www.sapgenie.com/abap/bapi/example.htm
    http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://techrepublic.com.com/5100-6329-1051160.html#
    http://www.sap-img.com/bapi.htm
    http://www.sap-img.com/abap/bapi-conventions.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    http://www.sapgenie.com/abap/bapi/example.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    Regards
    Anji

  • Trusted RFC not working for different user , working for same user

    Dear All,
    I have two SAP system - One Solman (7.0) and another ECC 6.0 (SR3) on HPUX box with Oracle DB (Unicode).
    I want to establish Trust relationship between these system.
    I have configured the same, as per the following link:
    http://help.sap.com/saphelp_nw04/helpdata/en/8b/0010519daef443ab06d38d7ade26f4/content.htm
    and note 128447.
    My requirement is one user X in solman client 001,
    will execute some test plan (Tcode stwb_2) which will take the control to ECC 6.0 client 200, execute the tcode as user Y and come back in Solman again.
    The user X (SAP_ALL) exists in Solman - client 001 and user Y (SAP_ALL) exists in ECC 6.0 - client 200.
    In ECC 6.0 client 200, I have created a role ZRFCACL with the following and assigned to the user Y (as per the above help / note):
    Role : ZRFCACL
    Auth. Obj: S_RFCACL
    Value assigned to fields are:
         RFC_SYSID : SOL
         RFC_CLIENT: 001
         RFC_USER  : X
         RFC_EQUSER: N
         RFC_TCODE : *
         RFC_INFO  : *
         ACTVT     : 16
    Whenever the user  X is trying to execute the test from solman, he is getting the error : "No authorization to log on as trusted system (RC = 0)"
    Each time the user is trying the above, in ECC 6.0, the following dump is occuring:
    CALL_FUNCTION_SINGLE_LOGIN_REJ under username SAPSYS
    I have assigned the role ZRFCACL to user X in Solman also.
    Next, I have performed the following check:
    created one user M in both system
    created the role ZRFCACL2 in ECC 6.0 client 200 as follows and assigned the role to user M:
         Role : ZRFCACL2
         Auth. Obj: S_RFCACL
         Value assigned to fields are:
              RFC_SYSID : SOL
              RFC_CLIENT: 001
              RFC_USER  : ''
              RFC_EQUSER: Y
              RFC_TCODE : *
              RFC_INFO  : *
              ACTVT     : 16
    Assigned SAP_ALL to user M in both system (So the user M in Solman does not have ZRFCACL2).
    This time, the trust relationship worked and no dump got generated.
    I have also checked the thread Trusted RFC do not work
    but unable to resolve the issue.
    Any suggestion where the things are going wrong in this / what else I need to check or this is not possible at all?
    Thanks in advance for your help.
    Sudip

    Hi Valdecir,
    Thanks for the reply. I am providing the detail of the generated dump below:
    Please check in case any clue is there.
    Runtime Errors         CALL_FUNCTION_SINGLE_LOGIN_REJ
    Date and Time          12.08.2008 18:59:32
    Short text
    No authorization to logon as trusted system (Trusted RC=0).
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPMSSY1" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    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 RFC call (Remote Function Call) was sent with the invalid user ID "98819 "
    . Or the calling system is not registered as trusted system in the
    target system.
    How to correct the error
    The error code of the trusted system was 0.
    Meaning:
    0    Correct logon as trusted system mode
    1 No trusted system entry for the calling system "SOL " or the
    security key entry for the system "SOL " is invalid
    2 User "98819 " does not have RFC authorization (authorization object
    (S_RFCACL) for user "98819 " witl client 001.
    3    The timestamp of the logon data is invalid
    The error code of the SAP logon procedure was 1.
    Meaning:
    0    Login was correct
    1    Wrong password or invalid user ID
    2    Locked user
    3    Too many attempted logons
    5    Error in the authorization buffer (internal error)
    6    No external user check
    7    Invalid user type
    System environment
    SAP-Release 700
    Application server... "gcbeccd"
    Network address...... "10.10.4.158"
    Operating system..... "HP-UX"
    Release.............. "B.11.23"
    Hardware type........ "ia64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "gcbeccd"
    Database type..... "ORACLE"
    Database name..... "RD3"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Apr 5 2008 00:55:24"
    create on........ "HP-UX B.11.23 U ia64"
    Database version. "OCI_102 (10.2.0.1.0) "
    Patch level. 146
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "HP-UX B.11"
    Memory consumption
    Roll.... 16192
    EM...... 4189840
    Heap.... 0
    Page.... 0
    MM Used. 1194640
    MM Free. 2992576
    User and Transaction
    Client.............. 000
    User................ "SAPSYS"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "489F2BD6C36D0F12E10000000A0A049E"
    Program............. "SAPMSSY1"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "SOL"
    Database Release.... 700
    Kernel Release...... 700
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchron and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. 001
    User................ 98819
    Transaction......... "SMSY"
    Call Program........."SAPLSRTT"
    Function Module..... "SCCR_GET_RELEASE_NR"
    Call Destination.... "SM_RD3CLNT200_TRUSTED"
    Source Server....... "gcbsolm_SOL_00"
    Source IP Address... "10.10.4.206"
    Additional information on RFC logon:
    Trusted Relationship "X"
    Logon Return Code... 1
    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 "SAPMSSY1" - in
    "REMOTE_FUNCTION_CALL".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 67
    of the (Include) program "SAPMSSY1".
    Source Code Extract
    Line
    SourceCde
    37
    endmodule.
    38
    39
    module %_rfcdia_call output.
    40
    "Do not display screen !
    41
    call 'DY_INVISIBLE_SCREEN'.
    42
    perform remote_function_diacall.
    43
    endmodule.
    44
    45
    module %_cpic_start.
    46
    if sy-xprog(4) = '%RFC'.
    47
    perform remote_function_call using rfctype_external_cpic.
    48
    else.
    49
    call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
    50
    perform cpic_call using convid.
    51
    endif.
    52
    endmodule.
    53
    54
    55
    form cpic_call using convid type c.
    56
    communication send id convid buffer header.
    57
    if sy-subrc eq 0.
    58
    perform (sy-xform) in program (sy-xprog).
    59
    else.
    60
    message a800.
    61
    endif.
    62
    endform.
    63
    64
    form remote_function_call using value(type).
    65
    data rc type i value 0.
    66
    do.
    >>>>>
    call 'RfcImport' id 'Type' field type.
    68
    if sy-xprog = 'JAVA'.
    69
    system-call plugin
    70
    id 'JAVA' value 'FORW_JAVA'
    71
    id 'RC'   value rc.
    72
      if there is no rollout on the JAVA side which
    73
      rolls both, JAVA and ABAP, we return to the
    74
      C-Stack and reach this point
    75
    76
      in case there was an rollout, the ABAP-C stack is lost
    77
      and we jump direkt to this point
    78
    79
      here we trigger the rollout on this Abap side with
    80
      the following statement
    81
    system-call plugin
    82
    id 'JAVA' value 'ROLL_OUT'
    83
    id 'RC'   value rc.
    84
    else.
    85
    perform (sy-xform) in program (sy-xprog).
    86
    rsyn >scont sysc 00011111 0.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    1
    SY-TABIX
    0
    SY-DBCNT
    1
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    CPIC and RFC Control
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080812
    SY-UZEIT
    185932
    SY-XPROG
    SAPRFCSL
    SY-XFORM
    READ_SINGLE_LOGIN_DATA
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    2 FORM         SAPMSSY1                            SAPMSSY1                               67
    REMOTE_FUNCTION_CALL
    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
    %_RFC_START
    Chosen variables
    Name
    Val.
    No.       2 Ty.          FORM
    Name  REMOTE_FUNCTION_CALL
    %_DUMMY$$
    0000
    0000
    2222
    0000
    SY-REPID
    SAPMSSY1
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454555322222222222222222222222222222222
    310D339100000000000000000000000000000000
    SYST-REPID
    SAPMSSY1
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454555322222222222222222222222222222222
    310D339100000000000000000000000000000000
    HEADER
    000000000000
    000000000000
    TYPE
    3
    0000
    0003
    SY-XPROG
    SAPRFCSL
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5455445422222222222222222222222222222222
    3102633C00000000000000000000000000000000
    %_ARCHIVE
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    RC
    0
    0000
    0000
    SY-XFORM
    READ_SINGLE_LOGIN_DATA
    000000000000000000000000000000
    000000000000000000000000000000
    544455444445444445445422222222
    2514F39E7C5FCF79EF414100000000
    %_SPACE
    0
    0
    2
    0
    No.       1 Ty.          MODULE (PBO)
    Name  %_RFC_START
    %_PRINT
    000                                                                                0###
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    RFCTYPE_INTERNAL
    3
    0000
    0003
    Internal notes
    The termination was triggered in function "ab_xsignon"
    of the SAP kernel, in line 2491 of the module
    "//bas/700_REL/src/krn/rfc/absignon.c#9".
    The internal operation just processed is "CALY".
    Internal mode was started at 20080812185932.
    Calling system.....: "SOL "
    Caller.............: "98819 "
    Calling client.....: 001
    RFC user ID........: "98819 "
    RFC client.........: 200
    Trusted return code: 0
    Logon return code..: 1
    Transaction code...: "SMSY "
    Active state.......: "-782823270"
    Note: At releases < 4.0, the information for the caller is not
    available.
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    (0)  0x4000000003b2b450  CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
    (1)  0x4000000004d2c470  Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
    (2)  0x4000000004d32160  ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
    (3)  0x4000000002b43cb0  SignOnDumpInfo + 0x280 at absignon.c:2491 [dw.sapRD3_DVEBMGS00]
    (4)  0x4000000002b3f2f0  ab_xsignon + 0xb30 at absignon.c:876 [dw.sapRD3_DVEBMGS00]
    (5)  0x4000000002aa4cb0  ab_rfcimport + 0x1ad0 at abrfcfun.c:3599 [dw.sapRD3_DVEBMGS00]
    (6)  0x40000000040f4a80  Z8abjcalyv + 0x500 [dw.sapRD3_DVEBMGS00]
    (7)  0x400000000402f190  Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
    (8)  0x4000000003f538b0  Z9abxeventPKt + 0xb0 at abrunt1.c:281 [dw.sapRD3_DVEBMGS00]
    (9)  0x4000000003f360a0  ab_dstep + 0x280 [dw.sapRD3_DVEBMGS00]
    (10) 0x4000000001cb4600  dynpmcal + 0x900 at dymainstp.c:2399 [dw.sapRD3_DVEBMGS00]
    (11) 0x4000000001cab0e0  dynppbo0 + 0x280 at dymainstp.c:540 [dw.sapRD3_DVEBMGS00]
    (12) 0x4000000001cb1ec0  dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
    (13) 0x4000000001c9dff0  dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
    (14) 0x4000000001fea460  Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
    (15) 0x4000000001fb4de0  TskhLoop + 0x4e20 at thxxhead.c:4518 [dw.sapRD3_DVEBMGS00]
    (16) 0x4000000001faae40  ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
    (17) 0x4000000001569ec0  DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
    (18) 0x4000000002c10630  nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
    (19) 0x4000000002c105c0  main + 0x60 [dw.sapRD3_DVEBMGS00]
    (20) 0xc00000000002be30  main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
    List of ABAP programs affected
    Index
    Typ
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    SAPMSSY1
    0
    11.04.2005
    09:27:15
    22528
    E
    1
    Prg
    SAPLSCCA
    1
    05.07.2005
    13:10:18
    52224
    E
    2
    Prg
    SAPRFCSL
    0
    13.02.2005
    17:31:45
    17408
    E
    3
    Typ
    RFCSYSACL
    0
    13.02.2005
    17:31:45
    7168
    4
    Typ
    SYST
    0
    09.09.2004
    14:18:12
    31744
    Directory of Application Tables
    Name                                     Date       Time       Lngth
    Val.
    Program  SAPMSSY1
    SYST                                       .  .       :  :     00004612
    \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0\0
    Program  SAPRFCSL
    RFCSYSACL                                  .  .       :  :     00001760
    SOL                             RD3
    ABAP Control Blocks (CONT)
    Index
    Name
    Fl
    PAR0
    PAR1
    PAR2
    PAR3
    PAR4
    PAR5
    PAR6
    Source Code
    Line
    116
    CLEA
    00
    0035
    SAPMSSY1
    60
    117
    CLEA
    00
    0036
    SAPMSSY1
    60
    118
    CLEA
    00
    0037
    SAPMSSY1
    60
    119
    MESS
    00
    001C
    SAPMSSY1
    60
    120
    ENDF
    00
    0000
    SAPMSSY1
    62
    121
    00
    0000
    SAPMSSY1
    62
    122
    PERP
    00
    0001
    SAPMSSY1
    64
    123
    PERP
    02
    0000
    SAPMSSY1
    64
    124
    WHIL
    00
    0002
    0000
    0000
    0000
    0000
    0000
    0000
    SAPMSSY1
    66
    128
    WHIL
    00
    0003
    0000
    0000
    0000
    0000
    0000
    0000
    SAPMSSY1
    66
    132
    BRAN
    05
    001E
    SAPMSSY1
    66
    133
    CALY
    00
    0003
    0038
    002A
    0005
    002B
    0000
    0000
    SAPMSSY1
    67
    >>>>>
    CALY
    02
    0000
    0039
    8000
    0000
    0000
    0000
    0000
    SAPMSSY1
    67
    141
    COMP
    00
    0002
    0010
    003A
    SAPMSSY1
    68
    143
    BRAF
    02
    000E
    SAPMSSY1
    68
    144
    SRFC
    01
    0000
    003A
    003B
    SAPMSSY1
    69
    146
    SRFC
    01
    0000
    003C
    C000
    SAPMSSY1
    69
    148
    SRFC
    02
    0000
    0000
    0000
    SAPMSSY1
    69
    150
    SRFC
    01
    0000
    003A
    003D
    SAPMSSY1
    81
    152
    SRFC
    01
    0000
    003C
    C000
    SAPMSSY1
    81
    Thanks & Regards
    Sudip

Maybe you are looking for

  • SSL Private Key

    Hi, I would like to export my Portal private key, so that it can be used for network traffic capture (Wire shark). Can anyone point me in the direction as to where this file can be exported. Thanks Kai PS. Points will be awarded.....

  • List of packages with arch-specific patches

    Considering moving over from Fedora, having just learned about how many Fedora-specific patches are in their repositories.  (Installing vanilla glibc from source bricks my Fedora 22 installs, without incorporating the Fedora-specific patches - which

  • HELP! Lost work!!

    I was typing a paper on ipages when it closed without warning. I did not save before this happened. Is there anyway to get it back? Please I put a lot of work in to this I was so stupid not to save!

  • Using XML Transformations in CR Runtime or Viewer

    Using Crystal Reports 2008 I have created a report and written an XML Transformation to export the report when it's been run.  When I select the Export function I'm asked:    1. The Format (XML) and Destination (Disk File)    2. To choose and XML exp

  • Trouble getting numbers that I purchased from the Store for my MAC to get on my IPAD.

    I bought and downloaded Numbers for the iMac a couple years ago. I just bought an iPad and was told I could download numbers at no charge. I had the same problem with Pages, finally gave up and purchased it again as I needed it to get iCloud working.