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
Similar Messages
-
RFC Destination was incorrect,send complete BP Data again from CRM to R3
Hello All
Iam facing in issue in CRM - BP Application due to incorrect RFC Destination maintained for SAP R3.
Our CRM Testing system (CRO - Client 300) is connected to R3 Testing System (NCQ - Client 300), but when CRM system went for refresh, RFC Destination was overwritten, and due to that CRM system started pointing to wrong R3 server (NCD - Client 002).
Till we got to know the problem, User had created a BP in CRM and it had flown to incorrect server. later we corrected the RFC Destination , but now the issue is that If I make any small change in CRM BP data, Bdoc is going in error state and message says:
Messages for business partner 0090001677:
No customer is assigned to business partner 4A13ACE0AB356006E10000000A212
Entry 0500 does not exist in - check your entry
I tried to send BP data through middleware tCode /CRMM_Bupa_Send as well, but Bdoc gain got in error state saying :
Entry 0500 does not exist in - check your entry
I think, these errors are coming because system is assuming that it has already sent the data to R3, and it expects certain data to be present in R3 system, which it is unable to find since data for corresponding BP is not present in SAP R3.
I there any way, transaction through which I can send complete BP data from CRM to R3??? Please help.
Edited by: Surbhi Goel on Jun 2, 2009 3:25 PMHi Surbhi,
Could you try transaction CRMM_BUPA_MAP in order to see what mapping the system thinks there is (if any). It then allows you to send (same as BUPA_SEND) or retrieve data. I guess this will run into the same error, but it might be worth a try.
Hope this helps.
Sincerely,
KZ -
No RFC destination is maintained for the port 'SAPERP'
Hi!
I am facing with a very strange thing.
I am implementing a File_to_IDOC scenario.
Therefore I created in XI system the appropriate Ports in tcode IDX1.
I use one business system with two clients (SAPERB100 and SAPERB200).
I defined there of course the appropriate RFC connections (RFC_IDOCERB100 and RFC_IDOCERB200).
Unfortunately when I go into tcode IDX2 and try to load metadata I get the following error:
No RFC destination is maintained for the port 'SAPERP'
Message no. IDOC_METADATA455
Diagnosis
No RFC destination has been maintained for logging on to this system for the port SAPERP.
This means that no structure information can be provided for this port.
Procedure
Maintain the required RFC destination for this port.
Can some one help me to solve this problem?
Thank you very much!
regards
HolgerHI Holger
You need to have a RFC destination created for XI server type 3 (ABAP) to push IDOC from ECC. Similarly you need RFC destination in XI towards ECC to load IDOC / RFC metadata.
Thanks
Gaurav -
How to create a z-table to maintain RFC destinations??
Dear Experts,
Can you please guide me to create a Z table where I can maintain RFC destinations??
Regards,
Mamai.Moderator Message: This is not a Web Dynpro ABAP question. Please only post questions in this forum which are directly related to Web Dynpro ABAP development. I am moving this thread to ABAP General.
-
Error in SPM (RFC Destination not been Maintained)
Hello,
I have created a request for Super user access of a Fire fighter ID: FF_Goods Receipt and it has been assigned to a fire fighter and when he tries to login it is giving me the error as "The Destiantion XXXX has not been maintained.
I have done the configuration related to SPM and assigned a RFC Destination in SPM Config.
Where we have to maintain the RFC destination in SPM?
Regards,
Kumar RayuduHi Kumar.
Yes we need to create RFC connection for SPM (backend System)
Check for Post installation document
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90280209-1e57-2b10-009c-d8d800f626c5
Regards
Gangadhar
Edited by: gangadhar hm on Sep 4, 2009 12:04 PM -
RFC destination is not maintained for object BUS6001 and method PRECHECKPAY
Dear all expert,
I am configuring the interface betweeb HR system and FI system.Both of them are R3/4.70.
In BD64 , I add many BAPIs to distrubtion model.But for object BUS6001 I got a error message like the titel .
After check the SM59 WE20 WE21 I am totally confused, because they are OK. I also check the communcation between with the two system by change a old IDoc and send it out to the FI system. It successfully processed.
Do you have any suggestions?
Thanks in advance!You need to create RFC destination for dialog calls. You probably only defined the RFC destination for BAPI calls.
-
Table to maintain RFC destination
Hi,
An RFC enable Function Module from R/3 is to be called in CRM system. I dont want to hard the RFC destination for the R/3 whn calling the FM. Is there any other table tht can b used for this?
Is there any other way to achieve this???
Regards,
SivagamiHi Sivagami,
Check the table RFCDES. This table will store all RFC destinations defined for your system. U can use the transaction SM59 to create the RFC destinations. But most of the developers dont have access to this transaction. So cotact ur basis team to define required RFC destinations.
Thanks,
Vinod -
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 .SHi 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 -
Error in Local Message System: RFC destination MB3AP1039 does not exist.
Error in Local Message System: RFC destination MB3AP1039 does not exist. Message was Not Created
Message no. BCOS088
Hi,
When iam creating a message from any system from HELP-CREATE SUPPORT MESSAGE it is throwing the above error message. Actually i need to send this message to SAP solution Manager Service Desk.
Can anyone help me in resolving the above issue.
Thanks & Regards,
Mirza Kaleemulla Baig.Dear friend
You have to of following option
1.Define Service Desk destination in the R/3 systems:
Note: for this you need to log in the R/3 system.
Create the RFC between the Solution manager and R/3 system (Login to the R/3 system)
2.a. Go to transaction SM30.
b. In table/view field, enter BCOS_CUST. Then press the Maintain Button. See example below:
c. Press the Continue button in the following screen:
d. You should see the following screen, no entries should be seen in the table. Press the New Entries button:
e. In the next screen, enter the following information:
In the RFC Destination you should point to your Solution Manager destination RFC.
0ss_msg w sm_bsmclnt_back cust620 1.0
shailesh -
HOw to find out the RFC destination from BW system to ISU
Hi,
Currently my requirement is to call a function module which is written in ISU (remote enabled) from BW system.
I am unable to find out the rfc destination from BW to ISU system.
In CRM we have table like smofparsfa1. Is there any table in BW which can provide me the ISU destination?
I need to compare the records stored in isu as well as in BW system.
I need to call a function module which will provide me the data from isu.
please help me in this regard.
KrishnaHi,
You can check it in SM59 if there are any RFC destinations for the above systems.
Alternatively ,check the table RFCDEST if any entries are maintained
Regards,
Lakshman. -
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,
SubhashHello 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. -
RFC destination Java = ABAP system to wrong system
Hello everyone,
I have a NW04 Java system (WebAs 640, SP19), which has an RFC destination to an ABAP system.
The strange this is this: we changed the target system of the RFC connection to a different one (let's say from SID1 to SID2), they have different system numbers, different host names and different gateways. Only user and password we kept the same, as that's easier to maintain.
We have a self developed java application which uses this RFC connection.
When we call the application using only the <b>not</b>-fully-qualified hostname the RFC connection to the old (SID1) is used, but the destination is defined with SID2.
However, when we use the fully qualified hostname in the URL, it works with SID2 (which is correct).
Does anyone have an idea why that happens and what we can do to prevent that?
Regards,
CorneliaHi Mantosh,
it's an RFC connection entered in Visual Administrator of the Java System (service Destinations), so there's no possibility to set an RFC type like in SM59.
Of course you're right concerning the hostnames, but I was wondering how that could happen. Normally, it should read the data which I configured in the RFC connetion and use that.
We deleted temporary files and cookies and all from the workstation were we started the browser, even rebooted the workstation, but no effect.
Do you know any cache were the java system could have the old data left?
Regards,
Cornelia -
I am doing a file--> XI --> IDOC R/3 4.6 scenario.
R/3 is there in SLD as business system with role as app system and the correspong logical system is maintained in SALE.
Do we still need to create an RFC destination for R/3 client in XI system. In ta: IDX1 in XI system, there is no port created for R/3.
When I test this scenario I got the follwing error.
Transaction IDX1: Port SAP_XIXXX, client , RFC destination contain errors.
Here port SAP_XIXXX is the tRFC port created in R/3 system by giving the RFC destination created in R/3 for XI system, which we want to use later to send an IDOC to R/3. I am assuming I dont need this port at all to post an IDOC to R/3.
Please advise.Here is my scenario...Sending a file from XI client 105 through XI Server which will be posted as an IDOC in R/3 client (File-XI-IDoc).
In XI:
Created RFC Destination for R/3 client (SM59)
Created Port in IDX1 for R/3 client and loaded metadata in IDX2
As in my receiver agreement, I already specified sending service as XI105 and receiving service as R/3client....
Do I need to create partner profile(WE20) for R/3 Client in XI Server?
Do I need to create partner profile(WE20) in R/3? If, yes, then the partner number in R/3 client should be my business sytem sending the file(XI client 105) or my XI Server client?
Also, since no Acknowledgement is reqd, I did delete the port I created in R/3 for XI Server. But, I am still getting the following error..
Transaction IDX1: Port SAP_xxx, client , RFC destination contain errors.
Here SAP_XXX is the port for RFC destionation pointing to XI, in R/3 client, which I deleted.
Thanks,
Steve
Message was edited by: Steve Hsu -
Hello Gurus,
Earlier we had 2 ECC systems in the landscape.
Purchase requisition A from APO system supposed use RFC destination 1 and reflect in Plant XXXX
Purchase requisition B from APO system supposed use RFC destination 2 and reflect in Plant YYYY
Now we have only 1 ECC system in the landscape. we have changed the publication settings accordingly. but preq still not getting transferred correctly to ECC system.
Debugging the code shows system trying use wrong RFC destination.
Is there any other configuration setting we are missing.
Please advise.
Thanks In Advance
ShyamHi Shyam,
Please find my suggestions in regards to respective configuration settings.
1) Did you delete the obsolete RFC destination(Logical System) from your landscape?
2) Did you correct the RFC destination of plant YYYY to RFC Destination1 (incase you scrap RFC destination2 from landscape)?
3) Check what is the Logical System that is maintained for the location YYYY from the table /SAPAPO/LOCMAP in APO system.
4) Similar check for the products in the table /SAPAPO/MATMAP.
5) Remove the obsolete ECC System from the BSG using T-code /SAPAPO/C2.
Post checking and correcting, do an intial transfer of locations via CIF from the current ECC system.
Thanks,
Santosh KB. -
Error in Local Message System: RFC destination 10.189.98.10 does not exist.
Error in Local Message System: RFC destination 10.189.98.10 does not exist. Message was Not Created
Message no. BCOS088
Hi,
When iam going inside the tcode SM30 in the satellite system and entering the destination ip of solution manager system and after that when iam creating a message from HELP-CREATE SUPPORT MESSAGE, then it is throwing the following error.
Can anyone please help me in the above issue.
Regards,
Mirza Kaleemulla Baig.Hi Mirza,
For the RFC destination don't enter the IP address,enter the RFC name,somthing like SM_SP1CLNT200_BACK which is maintained in sm59.
Revert for any clarifications.
Thanks and Regards,
Avinash.
Maybe you are looking for
-
TS3148 my computer has a lighting bolt and a hazard symbol on it and will not run anything
Can someone help me know what to do in this situation. My computer has a lightining bolt and a hazard s ymbol on a grey screen and it will not reboot or do anything
-
Using method MB_DOCUMENT_UPDATE of MB_DOCUMENT_BADI
Hello dear friends! I 'm trying to use the method MB_DOCUMENT_UPDATE for MB1B, but this method is not acessed when I'm using the transaction. I've tried to debug but it only pass in the code of the method MB_DOCUMENT_BEFORE_UPDATE. I need to create a
-
Is "Joins & For all entries" in same SQL Query Possible?
Hi all Professional, Can we use "Inner Joins" and "For All Entries In" in the same SQL Query. if possible then pls clarify this query. Here I am using three Transparent Table and fetching data from them. SELECT abukrs abelnr ahkont axref2 ashkzg awrb
-
10g 64 bit installation on Linux!!
i want to run runinstaller from a remote host (32 bit) to install a database on itanium server (64-bit). The installation file i have downloaded is for 64-bit Linux too. When i started ./runinstaller i could not succeed to start the script and i got
-
Disable "Do you wish to overwrite your local copy" prompt
Where is the option to disable the "Do you wish to overwrite your local copy?" prompt whenever I download a file from the remote server?