Charm TMS - RFC destinations

Dear friends,
How can I:
Create new RFC destinations ?
Regenerate or Modify RFC destination READ
Regenerate or Modify RFC destination TMW
Regenerate or Modify RFC destination Trusted
Regenerate or Modify RFC destination Login ?
Thanks in advance for your advices.

SMSY transaction helped me. Quite easy.

Similar Messages

Steps for RFC destination in TMS

Hi ,
I need to configure a transport system , First I need to set RFC destination.
I need to do a two system landscape. I need to set RFC destination for tis two systems only .
Is that I need to set a RFC destination(t-code SM59) in DEV as
DEV-DEV (DEV IP address)
DEV-PRD (PRD IP address)
In PRD as follows
PRD-PRD (PRD IP address)
PRD-DEV (DEV IP address)
I know we have to set a path :
DEV-DEV
DEV-PRD
PRD-PRD
PRD-DEV
as RFC Destinations, but where i need to set tis either in DEV or in PRD is my doubt.
In which client i need to login , for tis RFC destination creation . Is that i need to login in 000 client.
If i m wrong please correct me please..
Regards,
Hari

In a very simple terms
Yes! You have to login to client 000 for tme configuration.
1.you have to create the transport domain.<PRD>
2.Go to Dev and QA and run stms and add these systems to transport domain.
3.Again login to transport domain <PRD> and accept the system into the transport domain.
4.Later you can go to the graphical tool in transport domain and configure the transport route .
Dev-qa consolidation
qa to prd -delivery
and then distribute the configuration.
You dont need to worry about the rfc etc.It is automatic process.
Good Luck.
Amit

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

System cancel RFC destination - /TMWFLOW/TRACK_N107

Hello Experts,
In ChaRM, when i release transport request from DEV to QAS occurs the error below:
"System cancel RFC destination SM_D01CLNT210_TMW, Call The name or password ins't correct.
Message no. /TMWFLOW/TRACK_N107"
I've checked in the SM59 all connections to DEV and to QAS environment and all are OK.
What's wrong with my ChaRM? Is possible to be a autorization problem?
Thanks to all,
FS.

Hello Fabio
'SM_D01CLNT210_TMW'
check both, the connection test and the authorization test for the RFCs

Charam - System cancel RFC destination SM_GSPCLNT300_TMW, Call BAPI_USER_EX

While configuring charm for my prd rfc im getting following error.
System cancel RFC destination SM_GSPCLNT300_TMW, Call BAPI_USER_EXISTENCE_CHECK: Password logon no longer possible - too many faile d attempts
RFC connection of type SPACE does not exist
RFC connection of type S does not exist
RFC connection of type T does not exist
System cancel RFC destination SM_GSPCLNT300_TMW, Call BAPI_USER_EXISTENCE_CHECK: Password
Message from function module /TMWFLOW/CHECK_PRJ_CONS: No export system for GSP-300
Any solutions for this

Hi,
Please ensure RFC connection to GSPCLNT300 is working fine. You can go to SM59 to perform authorization testing. User & password set in RFC should match in GSPCLNT300. also, check logon group "SPACE" as well.
Thanks,
Nicholas Chang

An RFC destination could not be specified for the logical system

Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
Khushboo

Hi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo

Logical system and rfc destination

hello all,
what is the difference between logical system and RFC destination?
thanks for ur help in advance.
regards,
vikas

Hi,
In any ALE scenario u need one sender and one receiver system.
Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
Regards

Logical system and rfc destination related Query?

Hi Dudes
Do we need to define logical system and RFC destination if they are in different clients in same server
Regards
Raj Kumar

Hi
Both are client independent setting, so even if you define in one client, it would be available in other clients also.
Regards,
Sanjeev

RFC Destination Connection Pool requirement

Hi Experts,
I have a custom webdynpro java application to display number of work items pertaining to that particular user in a backend.
There are users who dont use this functionality as well. But the requirement is to place this application in home screen.
I have used both metadata and modeldata with hard coded user since we did not want error messages to appear for users who do not have backend access.
Application & Access Details
Application Location : Home Screen
Concurrent Users : 600 concurrent users maximum possible value
Connection Usage : Close connection immediately using disconnectIfAlive() method.
Now I need to configure JCO Pool Size , Max Connections, Wait Time for the RFC destination.
I have read a lot of post and documents but could not acheive clarity of thought on this.
Kindly let me know what values I should give in these fields for optimal performance and no connection issue for users.
Regards,
Porselvan

Hi Muthavudaiyan,
Hope you are doing good.
Basically from the JCo perspective, there are only 5 parameters that are involved here:
jco.destination.pool_capacity:
Maximum number of connections that are held open in the pool for reuse (default: 1)
jco.destination.peak_limit:
Maximum number of connections that can be obtained from a pool at peak usage times
jco.destination.max_get_client_time:
Maximum time to wait for a free connection if the peak limit is reached before exception is thrown
jco.destination.expiration_time:
Timeout period after which pooled idle connections can be closed (default: 600000ms = 10mins)
jco.destination.expiration_check_period:
Regular time interval for checking if pooled connections have expired and will be closed
The values are determined by the application in question. The ideal values have to told to you by the application developer; there are no two ways about this.
Thank you and have a nice day :).
Kind Regards,
Hemanth

Service desk RFC destination in the Satellite system

HI All,
can any body tell me the RFC destination that is to be maintianed in the satellite system so that the message reaches the solution manager service desk.
I am creating messages they are being send to the service desk successfully but are not visible when I go into the service desk of the solution.
But they are visible through the transaction code CRM_DNO_MONITOR .Can any body help the RFC destination to be maintaned in the BCOS_CUST table so that the message reaches the Service Desk.]
Currently I am using the RFC destination to the service desk client in the solution manager ie SIDCLNT200
Thanks in advance
Regards
Amit

Hi Amit,
I think your expectation is not correct. I understood, you can create a message in a satellite system and you can see the ticket in SolMan service desk. Then everything is configured correct. What you are now looking for is to see the ticket in a solution when the sat. system is part of the solution. This is not working. If you create out of a solution a service desk ticket, these ticket get a special attribute that they belong to this solution, all other tickets can not be selected by a solution.
Sorry but I am quite sure that it is working like this.
There is only one option, that you define special variants so you can see only tickets from special systems, but these variants can not be assigned to a solution.
Regards,
uDo

How to create a RFC destination for extracting data to HANA

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

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

Unable to change RFC destination in IT Performance reporting wizard

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

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

Communication failure : RFC Destination SALV_WD_EXPORT_PDF does not exist

Hi Experts,
I have one standard ALV report in ABAP Webdynpro.
When i try to print the ALV Report it gives Communication failure : RFC Destination SALV_WD_EXPORT_PDF does not exist.
Can you give solution for this one.
Regards,
Sri

Hi Sri
Please go through this..
/people/bv.pillai/blog/2007/01/09/webdynpro-abap-alv-print-versionpdf
also Have a look this note SAP NOTE 918236; you will need help from basis.
Cheers,
Kris.

How to find out, which RFC-Destinations are in use?

Hi community
We have a huge list of RFC-Destinations in our productive system and I want to delete unneeded entries.
Is there a report or a log, which shows, which RFC-Destinations were used, and when?
Thanks in advance.
Regards, Michael

HI
can you see the default trace in tcode SMGW, Be careful about deleting any system rfc.
Read the documentation about default RFC, internal RFC, LDAP_RFC, transport RFC.
I don't know other way to do that you need
Regards
William Neira

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

Charm TMS - RFC destinations

Similar Messages

Maybe you are looking for