RFC Destination name

Hi
I have created an RFC Destination of type 3 from XI pointing to SRM. Now I have to create another RFC Destination of type H pointing to the same SRM for using SRM as receiver proxy. Can I use same name for both RFC Destinations?
Will it create any error?
Radhika

>Can I use same name for both RFC Destinations?
Not possible with same name.
>I thought the format is System ID CLNT plus number.
You can go with any naming convention.
>Just a quick confirmation, do I have to create any RFC Destinations in SRM system pointing to XI? There is already an RFC Destination of type 3 created, connecting with XI
If its already there then why do you need to create. Use the same destination.

Similar Messages

RFC destination names and logical names

Hi,
I have an RFC connection set up in the DBCON table. Is there any way to test these connections? I tried using SM59 but I couldnt match the RFC destinations in SM59 with the connection names in DBCON?
Any help will be appriciated.
Thanks,
Praveen

Hi,
DBCON is the table for Database Connections storage. It has nothing to do with RFC connections ans so with SM59...
Regards,
Olivier

FM to get RFC destination name

Hi,
Could any body please let me know from CRM how can I find RFC destination of ISU ?
Thanks in Advance.

Hello Saba,
There is another easy way.
Call this:
cl_crm_isu_il_tools=>get_backend_dest(
    EXPORTING
      iv_check_avlbl = abap_true
    IMPORTING
      ev_backend_dest = gv_dest
      ev_available    = lv_available
    EXCEPTIONS
      no_backend_dest = 1
      OTHERS          = 2 ).
Or you can just execute it via SE24.
Best Regards,
Yevgen

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

Program ID in RFC destination-XI

Hi
can any one tell me
for RFC sender channel purpose i'm creating RFC destination in SM59. through sap help and some other weblogs i'm trying create Program iD,but i'm getting some doubts on this:
1. How do i know corrosponding programID for this register server program?
2.How do i know sender system is Unicode system is or not?
Auctully my scenrio is RC--->JDBC, thats the reason i'm trying to create RFC destination in r/3 side..
regards
rambarki

Hi Rambarki,
Is your scenario sysnchronous or asynchronous ?
if your scenario is asynchronous then from ABAP program you can call your RFC using the following syntax...
CALL FUNCTION 'RFCNAME'
DESTINATION 'RFCDESTNAME'
EXPORTING ...
IN BACKGROUND TASK .
for synchronous scenarios use this
CALL FUNCTION 'RFCNAME'
DESTINATION 'RFCDESTNAME'
EXPORTING ...
IMPORTING ...
You also try using SE37..
In SE37 enter name of your RFC and press on execute..
then enter your RFC destination name , input parameters..and execute.
Is test connection working fine in SM59 ?
Take look at this thread aswell
Re: How to test the RFC to Flat File scenario
Regards
Anand

RFC - XI - WEBSERVICES scenario - Where to create RFC Destination

Hi Experts
For my RFC - XI - WEBSERVICES scenario, I have to create one TCP/IP RFC destination on R/3 system with the following details
RFC Destination Name    : XXXX
Connection Type            : T (TCP/IP)
Activation Type              : u201CRegistered Server Programu201D
Program ID                      : YYYY
Gateway Host                : R/3 Details ..??
Gateway Service           : R/3 Details ..??
My Function Module (Remote-Enabled) - u201CZZZZu201D is defined in R/3 System.
This Function Module should be communicated with the target system i.e. NW XI system
As per the Note from SAP Help: To be able to communicate using RFC, you need to define the target systems as RFC destinations in the sending system(R/3)
Target system u2013 XI Server
Sending system u2013 R/3 System
Are my details provided are good enough as per my explanation? Please guide me in this regard.
QUESTION : Where exactly do I need to create the RFC Destination(SM59)? on R/3 side or on XI side?

Refer the following link-
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414700)ID1636235450DB01012070359836134304End?blog=/pub/wlg/1438
what are the inputs should be given to Gateway Host and Gateway Service while creating RFC Destination??
Open transaction SMGW on the R/3 system and choose
Goto -> Parameters -> Display. Beneath Attributes there will be the
entries 'gateway hostname' and 'gateway service'.#

Error in SWF_XI_CUSTOMIZING - Configure RFC Destination

Dear Experts,
Basis team is performing PI 7.1(EHP1 - SP04) readiness check. We are not able to activate Configure RFC Destination. Please refer the following attachment.
We have checked if WF-BATCH user got locked. It is fine and in unlocked status. Is there any setting which are missing? Thanks in Advance.
[http://www.flickr.com/photos/49754947@N07/4657473257/]
Thanks,
Phani Akella.

Hi Phani,
Create a RFC connection of type R/3 in the transaction SM59.
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f62cfa8911d386e70000e82011b8/frameset.htm
Or you may go to:
Tcode SM59 -> R/3 connections -> Create
1) Give RFC destination name.
2) Connection type - 3.
3) Technical settings tab -> Target Host -> give the Application Server name -> press enter.
The IP address automatically gets filled up.
4) Logon security tab -> Assign the Logon details.
Also, on the button of the image you posted there is a:
"No Language Can Be Defined for the RFC Destination"
Check for that too.
Regards,
Caio Cagnani

Finding RFC destinations

Hi ,
I am calling RFC functional module and I am passing the destination by Hardcoding . How can we pass the destinations dynamically .
For example i am pasing the destination like
CALL FUNCTION 'Z_PROMOTION_ON_ARTNR_ME_FIND' DESTINATION 'D01CLNT202'
In above case destination is 'D01CLNT202' this destination for Developement system whenever the code moved to qualaity i have to pass the quality destination system and then production means i have to pass production destination system.
How can i pass the destination dynamically . Is there any FM or method ?
Regards
Srihari

Hello,
I don't think there is any FM or method which can return you the RFC destination of the particular system!
You can specify the RFC destination dynamically by passing the value in a character-like variable, like this:
CALL FUNCTION 'Z_PROMOTION_ON_ARTNR_ME_FIND' DESTINATION gv_dest
You can use the following 2 approaches:
1. If there is a scope of User Interaction, you can create an screen-element where the user can i/p the RFC destination name(F4 help will help the cause). But there is a chance that the user may not be aware of the correct RFC dest.
2. You can create a TVARVC param & store the RFC destination against it. This has to be done in the QAS & PROD system as well. In your program you will have to query the TVARVC table using the parameter(this has to be hardcoded though!) & get the RFC dest.
I've implemented both these solutions, but find the latter more convincing. The end users are finicky when it comes to technical terms like "RFC", "FTP" et al.
@Keshav: How do you get the logical system for the QAS & PROD systems?
BR,
Suhas
Edited by: Suhas Saha on May 18, 2011 3:25 PM

Deciding RFC destination dynamically

Hello All,
I need to call a RFC which is there in R3 system from SRM system . While calling RFC I want to decide the RFC destination name dynamically i.e. depending upon the development , quality and production environment.
Is there any way to decide the RFC destination name dynamically depending upon the source and target system's logical system name or with some other way.
Thanks and regards,
Keith

This solely depends on the naming conventions you are using. Since the name of the RFC destination is arbitrary, there is 'no' way of determining the name of the destination.
To be flexible to some extend, I 'always' create a customizing table (which can be maintained without transport) in which I use a name (like name of function module which calls RFC) as key field. second field is the name of the destination.

How to get RFC Destination and Logical System name dynamically

Hi all,
I have a RFC FM written in CRM. I need to call this FM in R/3. So, i use the syntax " Call function <func> destination <destination name>. My problem is that i need to fetch the destination name dynamically..
There is a way to do so in CRM which is as follows:
DATA: lt_siteselect TYPE TABLE OF siteselect INITIAL SIZE 0,
           ls_siteselect TYPE siteselect.
CALL FUNCTION 'SMOF0_READ_SITESELECT'
    TABLES
      to_siteselect = lt_siteselect.
READ TABLE lt_siteselect INTO ls_siteselect
         WITH KEY sitetypeid = cl_smw1_siteprovider=>c_sitetype_r3oltp.
The above piece of code returns the site and also takes care of the client you are currently working on. But the specified FM is present only in R/3..
I want to achieve the functionality fulfilled by the above code in R/3.
Kindly help.
Useful answers will be rewarded.
Thanks in advance,
Karan Merwana
I can not use FM LOG_SYSTEM_GET_RFC_DESTINATION as for that i need to provide the logical system name. And the logical system name would be different for different clients.
Message was edited by:
        Karan Merwana

For those referring this thread later, I could not find a solution to this and ultimately had to do away with hardcoding of system names based on the DEV, Q, and PROD system names.
If anyone does manage to get a workaround, please let me know.

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

RFC destination Could not be SPecified for Logical System

Hello there
i am traying to costomize Transaction Luancher for some of the report which is been devloped in ECC (wich is ARD 100)
when on Transaction launcher Wizard--> techincal
i am having a logical system as ARD100(my r.3 system where report is devloped and which is connected to CRM )
while chosing the OBJ.TYpe :   and Method:
it says shows three erroe :
1) RFC destination could not be specified for the logical system ARD100
2) Object type and Method is not available
i have checked RFC , in SM59 entriesu2026u2026 There is an RFC named ARD100 and the connection test works. I also did an authorization test and it also works. I also checked to make sure the logical system name ARD100 exists
could you please help me to resolved the same
Regards
Rajiv

Hi Rajeev,
In a system landscape it's important and necessary to use the logical system names consistently throughout all systems!
Therefore please make sure, that you always use the same name for a logical system in all systems (CRM and R/3 systems).
The following steps are required before a RFC call is made from the CRM system to the R/3 system :
    o Use transaction SM59 to create an RFC destinations for the remote
       system.
    o Use transaction BD54 to create the logical system.
    o Use transaction BD97 to link the RFC destination created in SM59
       with the logical system created in BD54.
I hope this helps.
Best Regards
Gavin

Third Party (Garnishment) checks - RFC destination error

We have an issue with our testing of Third Party Garnishment checks. We have a split system, with our HCM system residing separately from the remaining ECC modules.
We are getting an error in regards to the printing of the checks in A/P.
The posting is working fine
the vendor account is cleared
However, It’s not creating a check # or check form.
We can do other check runs in this client fine; it’s just the 3PR runs that cause the error.
The text of the error message is as follows: An RFC destination could not be specified for the logical system HPQCLNT210.
We have exhausted our resources here looking into the RFC connection and the partner profile and we cannot find anything wrong with them.
Can someone offer suggestions on what else we could check? Thanks so much.

Hi David,
Did you check below is set-up correctly.
- Use transaction SM59 to create an RFC destinations for the remote system.
- Use transaction BD54 to create the logical system.
- Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
Also, check entries in TBLSYSDEST is filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
Thanks,
Ameet

RFC destination error in posting 3rd party payment in 4.7 FI system

Hi,
We are running in to a problem when we are processing a payment via transaction F110S in our R/3 4.7 system for Financials. We are integrating our Financial system with ECC6.0 for HCM. We receive 3rd party invoice from HCM successfully via ALE and post it in 4.7 system. When we try to process payment against this invoice, apparently 4.7 system is trying to communicate with ECC 6.0 system and issuing an error and the payment processing gets cancelled. It generates a clearing document with out a check.
The error says "An RFC destination could not be specified for the logical system HD1CLNT014
    Message no. B1550
Diagnosis
    An RFC destination should be specified for the logical system
    HD1CLNT014. This could not be done in this case. HD1CLNT014 is not your
    local logical system and this system is not included in the relevant
    Customizing tables.
Procedure
    Check:
        -   RFC destination
           -Port definition
         -oubound partner profile of message type SYNCH for this logical system
We checked our configuration for all Logical system and RFC destination and everything seems fine.
Any help in this regard is appreciated.
Thanks
Kesav

Hi David,
Did you check below is set-up correctly.
- Use transaction SM59 to create an RFC destinations for the remote system.
- Use transaction BD54 to create the logical system.
- Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
Also, check entries in TBLSYSDEST is filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
Thanks,
Ameet

Creation of RFC destination for SAP-Access Connectivity

Hi,
       I want to create a RFC destination for SAP-Access connectivity.
Can I get some help regarding it's connection type,activation type and gateway options required for the same.
Regrads,
Anthony D'souza

Hi
Please see the following:
1. Create an entry in Trxn DBCA for SQL Server in SAP, you are creating a database connection for the SQL server in SAP.
2. You use this connection, and write Native SQL stmnts...between EXECSQL...ENDEXEC to fetch the data..and then normal ABAP statements to put that data into your ztable.
TABLE DBCON Entry can be like this...depends on your External database..
CON_NAME          Raj                      Logical name for connection
DBMS                   MSS                   Microsoft SQL Server
USER_NAME        <User name>       For SQL Server
PASSWORD         <password>         " "
CON_ENV             MSSQL_SERVER=<server> MSSQL_DBNAME=<database name>
DB_RECO                 Availability type for an open database connect
FUNCTION z_houston_connect.
""Local interface:
EXEC SQL.
CONNECT TO 'RAJ' AS 'V'
ENDEXEC.
EXEC SQL.
SET CONNECTION 'V'
ENDEXEC.
*- Get the data from MS-SQL Server
EXEC SQL.
open C1 for
select
l.loc_id,
l.loc_name,
a.acc_id,
a.acc_name,
d.person
from ho_loc_mast as l
inner join snd_acc_mast as a on l.loc_id = a.loc_id
inner join snd_acc_addr as d on a.loc_id = d.loc_id and
a.acc_id = d.acc_id
where l.loc_id = '001'
ENDEXEC.
DO.
EXEC SQL.
FETCH NEXT C1 into :wa-c_locid, :wa-c_locname, :wa-c_acc_id, :wa-c_acc_name, :wa-c_person
ENDEXEC.
IF sy-subrc = 0.
PERFORM loop_output.
ELSE.
EXIT.
ENDIF.
ENDDO.
EXEC SQL.
CLOSE C1
ENDEXEC.
ENDFUNCTION.
Regards,
Raj

RFC Destination name

Similar Messages

Maybe you are looking for