ICM Problem - New Outgoing RFC Destinations Possible

Hi guys,
I have a problem with my ICM. I'm trying to configure Duet and was creating some outgoing HTTP Connections (to some web services). For some reason none works. It seems as if ICM is unable to resolve the target host. See following thread for more information:
I'd be grateful if someone has some input.
Cheers,
Jörgen

i checked your other thread as well. and i tried to simulate and here is my finding , try it out.
in the<b> Target Host</b> field just enter the address without the http:// prefix
(example www.webservicex.com)
and in the <b>Path Prefix</b> field enter the other details
(example /airport.asmx?wsdl)
now test the connection, it should work.
now change the Target Host to include http://, the connection will fail.
Try it out and let me know.
Regards
Raja

Similar Messages

Getting problem when creating RFC Destination on XI system

hi,
I m trying to create RFC Destination on XI system using sm59 tcode. In technical setting tab at Target Host field, i gave SAP ECC server IP address. and in Logon Tab I gave Login parameters for SAP ECC server (Client 400, User : 05 & Password for user 05). Current user and Unencrypted Password fields are unchecked. also Logon Scree is also unchecked in Security Option.
Problem is, when i click on Remote logon tab, It shows me Logon screen with client 000, User : 04 (which is XI system's user name) and Password. so it doesn't take given login setting for ECC system and if i tried this thing more than 3 times, ECC server block my pwd.
Please suggest me the required solution
Thanks & Regards
Ritesh

Hi ritesh
First check if the user exists in ths system. Check the password especially. Because the password space (Number of characters)in SM59 screen is more than password character in SU01 screen.Check the password.
Secondly, Check if you have given the proper client in the destination box of SM59.
Check for the unicode test also.
If possible change the user type as service user.
When everything is perfect am sure the rfc connection should be fine...

Delete RFC-Destination 'None' - Urgent

hi all,
I have a problem with the RFC-Destinations. In the Transaction SOLUTION_MANAGER i got the message "RFC-Destination NONE does not exist".
But I have created the Destination.
Then I found the SAP Note 61888.
description:
If the destinations NONE, BACK or SAPGUI are inadvertently deleted, they must be recreated:
NONE : Type I, no further entries
But I cant recreate this Destination, I got the Message: "Not possible. Internal Connections will be generated".
Can please someone help me. It worked 8 weeks and now I got this failure.
Thx
LM

have a look at this sap note: 181591
"Each time an application server of an R/3 System is restarted, the RFC destinations of type I (internal connection) in this R/3 System are maintained again. The following rules apply:
1. There are always the destinations NONE and BACK which point to the respective application servers themselves."
maybe the restart will take care of it?
read the SAP note please
Regards,
michal

PROBLEM WITH RFC DESTINATION

Hi GURU,
I have a problem with the record of RFC destination.
When i created RFC destination TCP/IP when i made the tests, it`s ok.
But when i used this rfc destination in a function of ABAP. I have an error. The error is:
RfcExecProgram'#Win32 error 2: The system cannot find the file speci
Can you help me??
What should I do to run properly?
Thank for all.
regards,
RAFA

Hi,
Even I am also new to SAP , but I have little knowledge about RFC, try to create your RFC of type 3 (ABAP type ), then if you use this RFC , I hope no problem will come if the authorization details and IP /Host name of the destination system are perfect.
also Please suggest me why ( when ) we use TCP /IP type of RFCs

Creation of RFC Destination problem

Hi Experts,
I need to establish an RFC communication between TREX7.0 server running on windows 2003 server and the SAPR/3 4.7 EE server running on windows2000.
server. Initially i used TREXAdminTool to create RFC Destination, i was unable to create successfully
Then i used SAPR/3 server from TCODE: SM59, here also am facing the same problem, what are the values i have to give for
1. RFC Destination, 2. Program id 3. Gateway Host and Gateway Service.
PLZ guide me step by step procedure with some example values to create RFC Destination to TREX Server successfully using TREXAdminTool or from SAPR/3 server---SM59
ADV Thanks
Regds
phanikumar

Hi,
Till now i didn't install explicitly any SAP Gateway on TREX server.
I installed TREX server along with SAP Netweaver WEB AS java.
Shall i need to install any SAP Gateway to configure RFC Destination?
If so can you give me the procedure how to install explicitly SAP gateway?
Regds
Phanikumar

Rfc Destination problem in RFC Sender Adapter

Hi experts
I created a Rfc destination type TCP/IP for Rfc Sender adapter.
while creating i passed following parameter:
1) I selected Activation Type option-> Registered Server
2)Given a Program id , same as i given in Rfc sender Adapter config.
3)Gateway option:
   i) Gateway Host:Server IP address where i created Rfc.
ii) Gateway Service:sapgw00
After making these entry, i m unable to receive message at XI end (I am executing Rfc at R/3 site due to Rfc sender)

Hi
please check for the following things.
1. check the RFC destination using the connection test tab in the R/3 system.
2. check whether the program id that u have given is registered or not.
to check the program id go to the transaction SMGW, in the menu select Goto-->LoggedonClients
check for ur program id name in the table.
3. when you configure the RFC sender adapter in XI then you have to give the same program id name that you will give while creating the RFC destination in the R/3 system.
if u still face the problem please reply me back.
Thanks
Rinku

HTTP with RFC destination problem

Hi,
We're doing an SAP R/3 --> XI --> External System scenario. We've had no problems making the SAP R/3 to XI work. For XI to External System, we're using the Plain HTTP adapter with an RFC destination. The Server, Intermediate and Root CA of the External System have been already installed on the ABAP layer of XI using the transaction STRUST/STRUSTSSO2 . The Server Certificate and Root CA of XI have also been installed on the External System Server. The problem is that everytime we test the RFC destination, we are still getting an ICM_HTTP_SSL_ERROR
Additional Parameters:
SSL has been enabled on the RFC destination
All three certificates can be found in STRUST
Regards

HI
is the certificate same for both of you have installed external system certificate and external system have PI certificate
Check SAP note 510007
Check similar threads
ICM_HTTP_SSL_ERROR
ICM_HTTP_SSL_ERROR for plain HTTPS with RFC Destination type G
Thanks
Gaurav

Post Install Activities Problem - Checking RFC Destination

I "successfully" installed Web AS 6.4 SR1 ABAP Non-Unicode. I am following the instructions in SAP Web Application Server 6.40 SR1 ABAP on Windows: MS SQL Server guide. The Post Installation instructions (2.2.6) require that I Check the RFC Destinations if my the database is located on a remote server from the central instance server.
The instructions tell me to locate the SAPOSCOL_<DB_Hostname> under the TCP/IP connections and if I cannot locate it I must add it.
In my case I cannot locate it so I want to add it. However, I do not know what data I must enter in the various fields of the RFC Destination screen. Example: what is the connection type for SQL Server
Thank you.

Hi Doug,
Is your database installed on a separate host from the SAP software? If not, you can safely ignore this recommendation and move on.
We have many systems on Win / MSS on 6.40 ABAP / Java with db and SAP on the same systems. None of my systems have this RFC, and I am not aware of any problems due to the lack there of.
Regards,
Sanket

RFC Destination Seetings Problem between R/3 and XI System

Hi...
In my RFC to File Scenario I cant see the messages in MONI......
When we create RFC destination through SM59.....we will fill gateway host and service
of R/3......Then we Configure the RFC Sender CC and fill same Program ID, Gateway host & service of R/3.
My doubt is,after this should I have to configure SM59 at XI side ???.....
I am getting confused in this RFC Settings between R/3 & XI....Can u explain the flow correctly.....
Please help me out.....
Thanks,
Sudheer.

Hello Sudheer,
1.Configure the Sender communication channel by giving the programId there,
2.You need to create RFC Destination at Sender R/3 system pointing to PI, there you need to mention the programId, specified in Sender CC,
3. In RFC destination you need to specify your XI system details for Host/ServiceName nameand gateway service .
Note: programId is case sensitive.
No need to create any RFC Destination in XI system.
check the following thread for further clarifications.
Re: TCP/IP connection for RFC sender adapter
Regards,
Prasanna

RFC destination problem in SWF_XI_CUSTOMIZING

Hi,
SWF_XI_CUSTOMIZING
While performing SAP XI customizing (Automatic workflow customizing) on the node Maintain Runtime Environment, the system is asking question like below..
Configure RFC Destination:
RFC user has wrong password. Synchronize password?
Thanks,

Hi Raja,
check the RFC destination from R/3 to XI and XI to R/3....
The Business Process Engine (BPE) processes integration processes at runtime. Since the BPE uses functions of the Workflow Engine and generates workflows from integration processes at runtime, you must customize the Workflow Engine automatically by using transaction SWF_XI_CUSTOMIZING before you can use the BPE.
also check ...
http://help.sap.com/saphelp_nw04/helpdata/en/cd/20bc3ff6beeb0ce10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/5c29eb96803e2be10000000a1553f6/frameset.htm
Regards
Biplab

TCP/IP RFC destination problem

Hi All,
During the RFC destination creation, im using TCP/IP connections.. So please tell me what should be filled for the following fields:
Program
Target Host
Save as          Hostname Ipaddress
Please let me knw what should be the required steps, since when i had provided some information in these fields and tried to test; it gives the following error:
Error Details     timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456 Timeout dur
Error Details     ERROR: timeout during allocate
Error Details     LOCATION: SAP-Gateway on host DELECC6IDES / sapgw00
Error Details     DETAIL: no connect of TP PROGRID from host DELECC6IDES.bcone.com after 20 sec
Error Details     COMPONENT: SAP-Gateway
Any valuable help?
Thanks
rohith

Dont worry
Sender Port is not mandatory. Only the target port is mandatory
In SM59,
-Have you given the connection type as 3
-In the Target Host, give the IP Address of the target server
-System Number is to be filled
-Now, go to the Logon/Security tab,
-Give the language
-Client
-Username and Password of the destination server
-Now. Save it.
-Test Connection.
Hope the information is helpful

Problem in connecting JCO destination in web dynpro

HI all,
I was installed sneak preview of Net weaver 6.4,
I want to do some web dynpro (java) programs which connect to back end systems.(R/3 system).
The R/3 system which I want to connect is at remote place, i have connectivity to that R/3 system using VPN connectivity. With this I am not having any problem. Since I am able to connect using User name and password, and able to do some transactions like RZ70, etc.
I developed an application which calls COMPANY_CODE_GET_LIST (BAPI function).
for the above requirement what I did was
(1)I created SLD setting.
(a)Web as Java (I am not having any problem to
Create this.
(b) Web as ABAP.
When i am trying to create
This, there are some steps like i need to go to SAP log in and I need to run the transaction RZ70. For this i need to create an enter in visual administrator>JCO RFC Provider>runtime-->Bundles i need to create an entry for RFC destination as well as Repository.
under RFC destination there are some fields which i need to enter those are (a)Program ID as mySLD (b) Gateway Host as 10.10.10.125 (c)Gateway service as sapgw00 (d)Number of processes as 1
Under Repository (a) Application server host 10.10.10.125 (b)system number as 00 (c)Client number as 100 (d)Language as en (e)user as ABCD (f)password as 1234
I haven't choused the check boxes Local bundle and Unicode and pressed the set button. So like this i created the RFC destinations. under the properties tab there is a property called RFC_DEFAULT_DESTINATION by default it was false so i made it as true. .
I also went to SLD Data Supplier,under Runtime tab , HTTP Settings , I mentioned
(a)Host: pava-vis75
(b) Port: 50000
(c) user: administrator
(d) password: abcd1234
RFC Settings, I mentioned as
(a)Gateway Host: 10.10.10.125 (which is SAP R/3 system)
(b)Gateway Service/Host: sapgw00
CIM Client Generation settings, as
(a)Host: pava-vis75
(b)Port (http/https):50000
(c) user: administrator
(d) Password : abcd1234
I tested the CIMClient Test by click the the button. I got the successful message.
Then I came back to HTTP settings and clicked the button with tilted arrow mark [This triggers data transfer to system landscape directory], for this also I got a successfully message.[data transferred successfully]
Next I been to SAPLOGON and went to RFC Destinations by using sm59 transaction. There under TCP/IP connections i been to SLD_NUC , opened this by double clicking that and under Technical settings for Program ID I had given the ID which I created at visual administrator [JCO RFC Provider] which is mySLD , under gateway options for Gateway Host as 10.10.10.125and Gateway service as sapgw00 then i tested the connection, it was also successfully.
Then I opened the SLDAPICUST and i created a new entry for maintaining the SLD Access Data by giving some couple of entries as
(a)Alias: vissldtest
(b)Host Name: pava-vis75
(c)Port: 50000
(d) user: administrator
(e) password: abcd1234
Then saved it.
Next I created sapmsUV0 3600/tcp entry at
WINDOWS\system32\drivers\etc\services file, and also there are some required entries which are already existing those are sapgw00 3300/tcp to sapgw99 3399/tcp , another entry starts from sapdp00s 4700/tcp to sapdp99s 4799/tcp , next entry starts from sapgw00s 4800/tcp to sapgw99s 4899/tcp and sapmsJ2E 3601/tcp .
I restarted the system, as well as server.
Now my problem is when I was trying to create JCO destination at web dynpro content administrator. For that I navigated as create JCO Destination Deployed Contentlocal-local/CompanyCodeGetList-Applications CompanyCodeGetList
I Choosed the JCO Connections tab- there are 2 entries those are
(1) COMPANY_CODE_MODEL
(2) COMPANY_CODE_RFC_METADATA
So I started creating connection for COMPANY_CODE_RFC_METADATA.
First one is
General data Name : COMPANY_CODE_RFC_METADATA
Client : 100
I didnt changed any default JCo pool configuration.
J2EE Cluster
There is a check box called Use Local J2EE engine J2E on pava-vis75 so I choosed that.
Connection Type
Dictionary Meta Data and application Data
I choosed the first one.
Then
Msg. Server Connection
Security
After these, I tried to test the connection by clicking the Test Connection.
It is saying the error as
First time
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service 'sapmsUVO' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
second time
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service '?' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
Can any body please help me to solve this problem.
From past 1 week on wards I have been trying to resolve this. But in vain.

It does not necessarily mean that you have to change that parameter. I read that blog as I had a similar problem, and after reading it and understanding the reasons and possible causes for the error, I found that my particular problem was that I was using "PUBLIC" as the logon group in my JCO destinations, but such a group does NOT exist at my backend. I went to transaction SMLG, had a look at Logon Groups, noted that there were none other than SPACE, figured out that I had to include that information in SLD (Web AS ABAP tech. system --> Message Server --> Logon Groups), put it there. Voilá. It works.
Edit: That SPACE logon group is the one I had to use at JCO destinations. Sorry I forgot to mention that one...
Regards,
Eduardo.
Message was edited by: Jesus Cil

** End-to-End Monitoring - RFC destination error while save config in RWB

Hi Friends,
We have 2 RFC destinations in our XI server. 1) PMI<client>001 2) PMI<client><client>800. First one is for XI server. Next one is for Sender/Receiver System.
We want to activate End-to-End Monitoring in RWB. For this, when I save configuration, it throws the following error.
Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
I have checked the user in the above destinations. For the first destination, we have assigned PIRWBUSER of XI system. Test Connection is OK, but unable to login remote. At the same time, PIRWBUSER is not locked.
For the second destination, I have assigned some login user of sender/receiver system. Test connection is OK. Able to login remotely.
There is no RFC user in our XI system. (I tried using RFCUSER* thru SU01 tcode).
There is no PIRWBUSER in the Sender/Receiver System.
In RWB, Configuration, 3 components are there. 1) XIIntegrationServer 2) Business System (for Sender/Receiver System) 3) XI Adapter Framework. I selected last two. (First one is already selected). Monitoring Level : Medium (for all 3). Send and Receive Check box is selcted for the last two.
So, what could be the problem for the above error?
Could you kindly clarifiy friends.
Thanking you
Kind Regards,
Jeg P.

Hi friends,
I have one RFC Destination PMI<sysid>001. (Abap Connction) in my XI system. This destination is for XI server. Connection Test is OK. Remote Logon by using the PIRWBUSER is also ok.
In the 'Configuration' tab of the Runtime Workbench, when we select 'Save Configuration', (Business System and Adapter Framework is not activated) with the default activation for XI Integration Server, the system throws the following error.
Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
When we save configuration, an one more destination is automatically created in the name as below.
PMI<sysid>001<yyyymmdd>. For Example, PMIPID00120080207.
When we test newly created RFC destination, connection is OK, but not able to remot login using the same user PIRWBUSER.
The difference between old and new RFC destination, in old, we have selected Load Balancing is 'Yes', but in the new it is 'No'. The system also tells the error below.
Name or Password is incorrect (repeat logon) - PMIPID00120080207
But, still remote login is possible in the old RFC destination using the PIRWBUSER.
So, What could be the problem ...?
Kindly reply, friends.

No RFC Destination maintained

Hi Experts,
I am doing User Exit for MIGO.
I have done it successfully.but problem comes when the email is sent to the vendor, MIGO is getting DUMP.
So, to cross check i have remove the User Exit of MIGO. but to my surprise when i press POST button in MIGO the similiar DUMP comes.
So wht is the solution for this.
For your Information DUMP message is:
Runtime Errors         MESSAGE_TYPE_X
Date and Time          06.12.2007 14:57:55
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
No RFC destination is defined for SAP Global Trade Services
Long text of error message:
Technical information about the message:
Message class....... "/SAPSLL/PLUGINR3"
Number.............. 002
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLMBWL" or "LMBWLU21"
"MB_POST_GOODS_MOVEMENT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "vngsap1"
Network address...... "192.168.0.10"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "VNGSAP1"
Database type..... "MSSQL"
Database name..... "EC6"
Database user ID.. "ec6"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 20 2007 00:45:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "SQL_Server_8.00 "
Patch level. 102
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 21953056
Heap.... 0
Page.... 73728
MM Used. 15443024
MM Free. 1280936
User and Transaction
Client.............. 800
User................ "VEDHRUV"
Language key........ "E"
Transaction......... "MIGO "
Transactions ID..... " "
Program............. "SAPLMBWL"
Screen.............. "SAPLMIGO 0001"
Screen line......... 18
Information on where terminated
Termination occurred in the ABAP program "SAPLMBWL" - in
"MB_POST_GOODS_MOVEMENT".
The main program was "SAPLMIGO ".
In the source code you have the termination point in line 59
of the (Include) program "LMBWLU21".
Source Code Extract
Line
SourceCde
29
   when a goods movement for an inbound or outbound delivery is posted
30
   directly from VL31N/ VL01N, XBLNR is not yet known when we call
31
   CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
32
   BKPF as well. There is no other way to forward XBLNR to FI as not
33
   every document is posted by MB_CREATE -> a new function module in
34
   MBWL for transferring the information, called by FI, meant to load
35
   the complete function group for all MBxx postings when this isn't
36
   required (Performance). Would be the better way to transport the
37
   information after switching off MBxx in later release.
38
   corresponding IMPORT ... FROM MEMORY ... can be found in
39
   AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
40
l_mem_id = 'MKPF-XBLNR'.                                   " 641365
41
EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
42
ENDIF.
43
IF xmkpf-xabln IS INITIAL.                               "note 434093
44
CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
45
ENDIF.                                                   "note 434093
46
47
ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
48
49
ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
50
CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
51
EXCEPTIONS
52
error_message = 4.
53
As soon as we have started to put things into UPDATE TASK, we must
54
ensure that errors definitely terminate the transaction.
55
MESSAGE A is not sufficient because it can be catched from
56
external callers which COMMIT WORK afterwards, resulting in
57
incomplete updates. Read note 385830 for the full story.
58
IF NOT sy-subrc IS INITIAL.
>>>>>
MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
60
sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
61
    MESSAGE A263.
62
ENDIF.
63
Optische Archivierung
64
Spaete Erfassung mit Barcode
65
Redesign of barcode handling -> note 780365
66
PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
67
xmkpf-mjahr
68
barcode.
69
70
MOVE-CORRESPONDING xmkpf TO emkpf.
71
CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
72
EXCEPTIONS
73
error_message = 4.
74
MOVE-CORRESPONDING xmkpf TO emkpf.
75
CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
76
EXCEPTIONS
77
error_message = 4.
78
IF NOT sy-subrc IS INITIAL.
Contents of system fields
Name
Val.
SY-SUBRC
4
SY-INDEX
1
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
MIGO_STATUS
SY-UCOMM
OK_POST1
SY-TITLE
Goods Receipt Purchase Order 4500017132 - shah
SY-MSGTY
X
SY-MSGID
/SAPSLL/PLUGINR3
SY-MSGNO
002
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20071206
SY-UZEIT
145755
SY-XPROG
SAPLBPFC
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
7 FUNCTION     SAPLMBWL                            LMBWLU21                               59
MB_POST_GOODS_MOVEMENT
6 METHOD       SAPLMIGO                            LMIGOKG1                              921
LCL_MIGO_KERNEL=>GOODS_MOVEMENT_POST
5 METHOD       SAPLMIGO                            LMIGOKD1                              309
LCL_MIGO_KERNEL=>DOCUMENT_OPERATION
4 METHOD       SAPLMIGO                            LMIGOKD1                                9
LCL_MIGO_KERNEL=>DOCUMENT_POST
3 METHOD       SAPLMIGO                            LMIGOST2                              124
LCL_MIGO_STATUS=>LIF_MIGO_FRAME~OKCODE_HANDLER
2 METHOD       SAPLMIGO                            LMIGOFR2                              172
LCL_MIGO_FRAME=>OKCODE_DISPATCH
1 MODULE (PAI) SAPLMIGO                            LMIGOPAI                               11
PAI_OKCODE_DISPATCH
Chosen variables
Name
Val.
No.       7 Ty.          FUNCTION
Name MB_POST_GOODS_MOVEMENT
XBLNR_SD
2222
0000
0000
0000
EMKPF
000000000000000000          ##
2222222222333333333333333333222222222200222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
XMSSA[]
Table IT_3831[0x196]
FUNCTION-POOL=MBWLDATA=XMSSA[]
Table reference: 396
TABH+ 0(20) = 0000000088F26C31000000008C010000F70E0000
TABH+ 20(20) = 00000000C4000000FFFFFFFF04E90400E01B0000
TABH+ 40( 8) = 08000000C1108001
store        = 0x00000000
ext1         = 0x88F26C31
shmId        = 0     (0x00000000)
id           = 396   (0x8C010000)
label        = 3831 (0xF70E0000)
fill         = 0     (0x00000000)
leng         = 196   (0xC4000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000134
occu         = 8     (0x08000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
shmTabhSet   = Not allocated
id           = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
shmVersId    = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = 0x00000000
collHook     = 0x00000000
ext2         = 0x40F26C31
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xA0F5EA30
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
RRESWK
22222222222
00000000000
00000000000
00000000000
%_SPACE
2
0
0
0
L_MEM_ID
2222222222
0000000000
0000000000
0000000000
RSJOBINFO
00000000000000                                  ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
XMSPR_KEY
00000000
222222222222222222222222222222222222233333333
000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000
SCREEN
GODYNPRO-DETAIL_TAKE
4445455424454445544422222222222222222222222222222222222222222222222222222222222222222222222222
7F49E02FD45419CF41B500000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IT_RSTRUCT
Table[initial]
XMKPF-XABLN
2222222222
0000000000
0000000000
0000000000
%_DUMMY$$
2222
0000
0000
0000
SYST-REPID
SAPLMBWL
5454445422222222222222222222222222222222
310CD27C00000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ODM07M[]
Table[initial]
GT_GOCOMP
000000000000                                             ####              00000000000000
3333333333332222222222222222222222222222222222222222222220000222222222222223333333333333322222
000000000000000000000000000000000000000000000000000000000000C000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-SUBRC
4
0000
4000
L_ATPCB
22222
00000
00000
00000
XMKPF-MBLNR
5000011865
3333333333
5000011865
0000000000
0000000000
XMKPF-MJAHR
2007
3333
2007
0000
0000
BARCODE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T003
800WE50AMS         X                XX XXXXXH
3335433445222222222522222222222222225522555554222222
80075501D3000000000800000000000000008800888888000000
0000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000
KNVV
00000000                     000
2222222222222222222222222222222223333333322222222222222222222233322222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T064B
2222222222222222222222
0000000000000000000000
0000000000000000000000
0000000000000000000000
VGMSEG[]
Table[initial]
No.       6 Ty.          METHOD
Name LCL_MIGO_KERNEL=>GOODS_MOVEMENT_POST
ES_EMKPF_OLD
5000011865200700000000000000          ##
3333333333333333333333333333222222222200222222222222222222222222222222222222222222222222222222
5000011865200700000000000000000000000010000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
SYST-REPID
SAPLMIGO
5454444422222222222222222222222222222222
310CD97F00000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_EMKPF
000000000000000000          ##
2222222222333333333333333333222222222200222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OREF_TITLEBAR
|
| E0001000 |
| 60009000 |
| LS_EMKPF-SUBRC |
| 0 |
| 0000 |
| 0000 |
| C_MOD_ON |
| 1 |
| 3 |
| 1 |
| 0 |
| 0 |
| GOITEM-ERFMG |
| 0.0.0.0.0.0.1. |
| 0001000 |
| 000000C |
| LS_EMKPF-MBLNR |
| |
| 2222222222 |
| 0000000000 |
| 0000000000 |
| 0000000000 |
| SY-XPROG |
| SAPLBPFC |
| 5454454422222222222222222222222222222222 |
| 310C206300000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY-REPID |
| SAPLMIGO |
| 5454444422222222222222222222222222222222 |
| 310CD97F00000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY-MSGID |
| /SAPSLL/PLUGINR3 |
| 25455442545444532222 |
| F3103CCF0C579E230000 |
| 00000000000000000000 |
| 00000000000000000000 |
| TV_GODEFAULT_TRANSFER-CX |
| <initial> |
| <initial> |
| <initial> |
| SPACE |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| SY-MSGNO |
| 002 |
| 333 |
| 002 |
| 000 |
| 000 |
| SY-MSGV1 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| ES_EMKPF_OLD-MSGV1 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| SY-MSGV2 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| SY-MSGV3 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| SY-MSGV4 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| GODEFAULT_TV |
| 101 GR goods receipt |
| 2222223332245266667276666772222 |
| 000000101007207FF43025359040000 |
| 0000000000000000000000000000000 |
| 0000000000000000000000000000000 |
| LS_EMKPF-MJAHR |
| 0000 |
| 3333 |
| 0000 |
| 0000 |
| 0000 |
| OREF_TIP |
|
D0002000
90006000
TV_GOSPLIT-CURRENT_LINE
<initial>
<initial>
<initial>
No.       5 Ty.          METHOD
Name LCL_MIGO_KERNEL=>DOCUMENT_OPERATION
I_SIMULATE
2
0
0
0
I_SIM_VALUES
2
0
0
0
I_ERROR_ONLY
2
0
0
0
E_OK
2
0
0
0
ET_XMSEG
Table[initial]
RSJOBINFO
00000000000000                                  ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
LS_EMKPF
5000011865200700000000000000          ##
3333333333333333333333333333222222222200222222222222222222222222222222222222222222222222222222
5000011865200700000000000000000000000010000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LT_EMSEG
Table IT_4407[2x744]
FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_EMSEG
Table reference: 460
TABH+ 0(20) = F06C0731F83FE73000000000CC01000037110000
TABH+ 20(20) = 02000000E8020000FFFFFFFF0400000040420100
TABH+ 40( 8) = 10000000C1308001
store        = 0xF06C0731
ext1         = 0xF83FE730
shmId        = 0     (0x00000000)
id           = 460   (0xCC010000)
label        = 4407 (0x37110000)
fill         = 2     (0x02000000)
leng         = 744   (0xE8020000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#001704
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xB8902E31
pgHook       = 0x00000000
idxPtr       = 0x00000000
shmTabhSet   = 0x00000000
id           = 3425 (0x610D0000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x00000000
collHook     = 0x00000000
ext2         = 0xE0D66931
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x00F11C31
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
LT_XMSEG
Table IT_4408[2x2364]
FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_XMSEG
Table reference: 464
TABH+ 0(20) = A0BEF93070D7693100000000D001000038110000
TABH+ 20(20) = 020000003C090000FFFFFFFF0400000030310100
TABH+ 40( 8) = 04000000C1308401
store        = 0xA0BEF930
ext1         = 0x70D76931
shmId        = 0     (0x00000000)
id           = 464   (0xD0010000)
label        = 4408 (0x38110000)
fill         = 2     (0x02000000)
leng         = 2364 (0x3C090000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#001613
occu         = 4     (0x04000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x28DF3031
pgHook       = 0x00000000
idxPtr       = 0x00000000
shmTabhSet   = 0x00000000
id           = 3511 (0xB70D0000)
refCount     = 1     (0x01000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 4     (0x04000000)
lineAlloc    = 4     (0x04000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 2     (0x02000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x00000000
collHook     = 0x00000000
ext2         = 0x28D76931
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x90F4EA30
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
LT_IMSEG
Table IT_4396[2x2792]
FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_IMSEG
Table reference: 465
TABH+ 0(20) = D0D5693190D7693100000000D10100002C110000
TABH+ 20(20) = 02000000E80A0000FFFFFFFF04000000E0410100
TABH+ 40( 8) = 04000000C1308001
store        = 0xD0D56931
ext1         = 0x90D76931
shmId        = 0     (0x00000000)
id           = 465   (0xD1010000)
label        = 4396 (0x2C110000)
fill         = 2     (0x02000000)
leng         = 2792 (0xE80A0000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#001702
occu         = 4     (0x04000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xE01BC930
pgHook       = 0x00000000
idxPtr       = 0x00000000
shmTabhSet   = 0x00000000
id           = 3413 (0x550D0000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 4     (0x04000000)
lineAlloc    = 4     (0x04000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = 0xC8626B31
collHook     = 0x00000000
ext2         = 0x80626B31
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xD88C0331
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
LT_CANCEL
Table[initial]
ABAP_TRUE
X
5
8
0
0
LCL_MIGO_GLOBALS=>IF_BADI
|
| F0000000 |
| 70008000 |
| SYST |
| ######################################T##########################################ÿ##### C#### |
| 0000000000000000000000000000000000000050000000005000000000000000000000000000109000F00050240000 |
| 100010000000000000001000100010000000004000C0B0403000000000000000000000000000B00000F00080030400 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000040000000 |
| 00000000000000000000000000000000000000000000000010000000000000000000000000000000000000D000000C |
| LS_XMKPF |
| 80050000118652007WEWEPR20071206200712062007120614575300000000VEDHRUV |
| 3333333333333333354545533333333333333333333333333333333333333544455522222222222222222222222222 |
| 8005000011865200775750220071206200712062007120614575300000000654825600000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| ME |
|
F0000000
D0002000
%_SPACE
2
0
0
0
L_NO_ITEMS
2
0
0
0
TV_GODEFAULT-CX
<initial>
<initial>
<initial>
LCL_MIGO_GLOBALS=>CALLER_SYTCODE
MIGO
44442222222222222222
D97F0000000000000000
00000000000000000000
00000000000000000000
LCL_MIGO_GLOBALS=>RETAIL_CONSIGNMENT_ACTIVE
2
0
0
0
%_FSREG_001
No.       4 Ty.          METHOD
Name LCL_MIGO_KERNEL=>DOCUMENT_POST
E_OK
2
0
0
0
ME
|
| F0000000 |
| D0002000 |
| ABAP_FALSE |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| LCL_MIGO_GLOBALS=>EXTERNAL_CALL_LEAVE_AFTER_POST |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| %_ARCHIVE |
| |
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No.       3 Ty.          METHOD |
| Name LCL_MIGO_STATUS=>LIF_MIGO_FRAME~OKCODE_HANDLER |
| I_OKCODE |
| OK_POST1 |
| 4455455322222222222222222222222222222222222222222222222222222222222222 |
| FBF0F34100000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000 |
| OREF_BADI_LOG |
|
D0002000
5000A000
%_FSREG_001
%_PRINT
000                                                                                0###
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LCL_MIGO_GLOBALS=>KERNEL
|
| F0000000 |
| D0002000 |
| %_VIASELSCR |
| # |
| 0 |
| 4 |
| OREF_DETAIL_BATCH |
|
60009000
0000F000
GOSEARCH_PO
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No.       2 Ty.          METHOD
Name LCL_MIGO_FRAME=>OKCODE_DISPATCH
I_OKCODE
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
L_MSG_STRING
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
L_OKCODE
OK_POST1
4455455322222222222222222222222222222222222222222222222222222222222222
FBF0F341000000000000000000000000000000000000000000000000000000000

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

RFC Destination could not be created in TREX administration tool

Hi All,
Recently i installed the TREX server, I am trying to connect the ABAP system with the RFC connection. I entered all necessary data for the RFC connection it giving error as
RFC Destination could not be created.
To solve the above problem i created one RFC connection of type TCP/IP in ABAP server eventhough it is not solved.
Can i have the solution for the above problem?
Regards,
Vivek.

Hi Michale,
Thanks for your quick response; I tried all the mentioned possibilities in that help document, still i am facing the same problem.
It is giving the below error
Connect to SAP System failed.Possible reasons:
-Logon data incorrect
-Password is not uppercase(must also be uppercase)
-SAP system user locked
-SAP user not in specified client
-SAP User rights are insufficient
-SAP system not reachable
-saprfc.ini unavailable or entries incorrect
-TREXTcpipClient.ini section[communication],parameters rfcdestination, sapsystem not set
-SAP system Basis component below 6.20 or SP too low
-->check also latest TREXTcpiplient trace file entries.*
The above all are check by me everything is fine.
The below information from the saprfc.ini file
DEST=NPI
TYPE=B
MSHOST=server1
GROUP=server1_group*.
Is there any mistake, please let me know.
Regards,
Vivek.

ICM Problem - New Outgoing RFC Destinations Possible

Similar Messages

Maybe you are looking for