Export of RFC Destination

Hi All,
Can anyone tell me if I can export all my RFC destination information in a transport request or other form ?
Regards
Lauran

Hi,
You cannot transport RFC Destinations directly. But there is a way,
Create a new Transport Request. After you have created the transport click on the request and in menu choose Request/Task and then Display. Goto change mode.
In PGMID give the value R3TR
In Obj give value TABU
In Object Name give RFCDES.
After that double click on table name entry. You will come to the screen: Transport organizer:Change Key List.
Here choose insert line. A new line with table name and key as the column headers will come up.
Double click on the Bobject Field. In the next screen you will get options to fill in the key.
You can insert key as per your choice. If you want to transport all the RFC Destinations give '*'. If you want to transport a RFC Des called say 'ABC' give the key as 'ABC'.
Release the transport and import it in the target system.

Similar Messages

NWA RFC Destinations Mass Maintenance (creation, exporting, ...)

Hello,
I would like to be able to maintain a number of RFC Destination on different landscapes without having to create them manually on each server. Ex. I have 10 RFC (or other type) Destinations. I have 50 servers. I want to be able to duplicate the destinations by one of the following ways:
1- Export the destinations from one machine, and upload them to the others;
2- Maintain the destinations in a resource file, copy this file to the other machines, trigger a script that would create those destinations in my other machines NWA.
To my knowledge there is no standard feature in NWA that allows copying/exporting of RFC destinations.
Any suggestions?
Thanks!

I don't think is possible, I think you'll have to do this manually unfortunately.
Regards
Juan

Export or transport all the RFC destination from one system to another syst

Hi
Is there any method to Export or transport all the RFC destination from one system to another system

Hi,
the information is stored in table rfcdes.But there are also some other RFC*-tables which have some relations. Nevertheless the RFC-connectons will possibly not work anymore in the new system(depending on the release your systems are), as the passwords are stored in the Sec store with system-dependent keys.
b.rgds, Bernhard

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 error while importing a client request

Dear Experts,
We are trying to import a Client Export from our Prd system to Development System and we are unable to import the request as it pops up a RFC destination error.
We have checked the RFC in the Dev QAS and PRD related to TMSADM and all of them are working fine
FYI, We are able to release the transports from the development system and it can be moved till qas and prd . So the TMS Configuration is also good.
The data file and co file in the backend of development is the same size as that of the Prd system.
I am really stuck . Kindly suggest a solution . Please find the screenshots while importing
Regards,
Suratharajan .S

Hi Suratha,
Goto STMS->system overview and select the Communication tab.
Maintained the Instance number of the ASD system.
Once you maintained the instance number , you will able to see it in the RFC ASD.DOMAIN_ASD.
Also distribute the configuration after entering the instance number.
With Regards
Ashutosh Chaturvedi

RFC destination of receiver system

Hi Guys,
I am trying to do the shell creation from scracth, and now i have found on the RFC destination creation there are three RFC connection which needs to be define. But my question is in this step we dont have any receiver system becasue export files has not been generated yet that will come after this step, so how can i proceed.
Regards,
Subhash

Hello Subhash,
In the step 'Define RFC Destinations' you create the RFC destinations for the SAP systems that participate in your project (or subproject).
Yes, you are correct, since the target/receiver system is not yet created, you cannot establish a RFC for the same.
Please proceed by maintaining the following:
Server name, System number , Language, Client, Username and Password for the control and the sender system.
Best Regards,
Mridu.

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

FM for RFC destination

Hi All,
Iam working on CRM4.0 and SAPR3 4.6. I need to call a Function module which is RFC enabled in CRM from R3. currently iam hard coding the RFC destination. is there any FM that can get me a destination.
could some help me with this?
Thank u.
Suresh.

Hi Suresh,
You check the FM 'SMOF_READ_SMOFERPSH' in CRM system.
It should work...
<b>code:</b>
DATA: lv_oltp_destination TYPE rfcdest,
        lt_erpsites         TYPE TABLE OF smof_erpsh,
        ls_erpsites         LIKE LINE OF lt_erpsites.
read OLTP destination
CALL FUNCTION 'SMOF_READ_SMOFERPSH'
    EXPORTING
    I_ERPLOGSYS          =
    I_RFCDEST            =
    I_SITEID             =
      i_sitetypeid         = 'SMOF_ERPSITE'
    I_ALL_ERPSITES       =
    TABLES
      t_erpsites           = lt_erpsites.
READ TABLE lt_erpsites INTO ls_erpsites INDEX 1.
lv_oltp_destination = ls_erpsites-rfcdest.
IF lv_oltp_destination IS INITIAL.
    RAISE no_data.
ENDIF.
CALL FUNCTION (RFC FMNAME)
    DESTINATION lv_oltp_destination
    TABLES

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

Error: Transaction IDX1: Port SAPRP1, client ,RFC destination contain error

Hi All,
I am faceing the problem while executing the XI ,
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
============
It is showing this error and the idoc is not posting to the SAP. When i checked out the IDX2 i am not getting any such structure of our IDOC type, So do i need to create the structure manually, or will it create automaticallywhen the idocs willposted .
Is there any import and export option for this.
Please treat this as urgent , thanks in advance...

Hi Jay,
how did you create port using IDX1 ,I think you must have to follow the naming convention there.Any user given name might not work.
I think in your case , create port as SAPRP1 using IDX1.
can you you give a try with that.port name exactly same as SAPRP1.
you may also refer this link
http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

RFC Destination None Error for MIGO

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

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

Create a RFC destination with default pass word

hi folk,
I've a Z-program which creates a RFC destionation (SM59) with a default password. The RFC destination has been created successfully with all the necessary fields, but the pass word is not aticve.
I'm using this fucntion module to scramble the pass word.
slen = STRLEN( p_p_prfcpw ).
SET EXTENDED CHECK OFF.
    CALL FUNCTION 'HTTP_SCRAMBLE'
      EXPORTING
        SOURCE            = p_p_prfcpw
        sourcelen         = slen
        key               = key
     IMPORTING
       DESTINATION       = p_pw
I've got this message from SM59.
Error in conversion of user password for destination A3
Message no. SR131
Diagnosis
The upgrade to SAP Release 7.0 starts an XPRA program that converts passwords to secure storage. In certain cases, you may need to skip this procedure (for example, due to database locks during the upgrade). This can cause the passwords to become invalid.
Procedure
Enter the user password again.
Any clues what is going wrong or how to solve this situation?
Best regards
Linhng

hi Roberto,
Everything is working except the pass word is not "converted" when I create the RFC destination in my z-program.
So my question is still how do I create a RFC destination with the "correct" pass word.
I've tried the function module HTTP_SCRAMBLE to convert the pw and also without the FM.
Best regards
LinhNg

RFC destination and FM

Hi all
I need to call a FM by RFC.
It is possible to specify calling the FM the RFC destination logon parameters?
Bye
enzo

Hi,
You can call using only destination.
CALL FUNCTION 'RFC_READ_TABLE'
        DESTINATION IV_RFCDEST
    EXPORTING
      QUERY_TABLE           = IV_TABNAME
      ROWCOUNT              = IV_ROWCOUNT
    TABLES
      OPTIONS               = IT_OPTION
      FIELDS                = CT_FIELD_GENERIC
      DATA                  = CT_DATA
    EXCEPTIONS
      TABLE_NOT_AVAILABLE   = 1
      TABLE_WITHOUT_DATA    = 2
      OPTION_NOT_VALID      = 3
      FIELD_NOT_VALID       = 4
      NOT_AUTHORIZED        = 5
      DATA_BUFFER_EXCEEDED = 6
      SYSTEM_FAILURE        = 7
      MESSAGE
      CV_MESSAGE
      COMMUNICATION_FAILURE = 8
      MESSAGE
      CV_MESSAGE
      OTHERS                = 9.
regards
vijay

Creating a transport containing RFC destination entries

Hello,
I hope someone can help me. I'm trying to remember the 3-4 tables which need to be exported to recreate RFC destinations. We are performing a refresh of our test system. Rather than re-create all the RFC's I'd like to make a tranport of them now and re-import them after the refresh. Does anyone know which tables I need?
Thanks,
Ben

Hey Matt,
The link you sent points to the thread I just created.
Ben

ShellCreation -RFC destinations

When I run RFC Destinations I get only Control and sender system detail. Do we have to Add Central system and Receiver as well ? Thanks

No you dont need to add control or receiver.
During shell only two systems are required, one on which you run TDMS and other one is the sender system from which you want to export the data.
Shell process doesnot do any step in the receiver it just guides the user to do some manual steps.
I hope this info helps

Export of RFC Destination

Similar Messages

Maybe you are looking for