RFC Destination using ABAP / 4 driver

hi all
i want to create RFC Destination using ABAP / 4 driver (Transaction-SM59) so do anyone have detailed steps/any blog/code regarding that. Plz forward it.
Regards
Martin

Martin,
Hope this link is helpful
http://help.sap.com/saphelp_nw04/helpdata/en/89/45aad99715462abdf09ec503e151e7/frameset.htm
Regards
Kavitha

Similar Messages

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 not-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,
Cornelia

Hi 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

RFC destination using TCP/IP

hi all
do anybody have created new connction in TCP/IP using RFC in transaction SM59. or have any document for creating the same.
Regards
Martin

Hi,
Also see
Design in System A
1. Create a simple work flow in System A whose triggering event is set to the bussiness object of the bapi. hence when the bapi is used to changed currency, the work flow is started.
2. Have a work flow task in the work flow, which calls a simple rfc say ZRFC_handleChanges which takes in the changes as parameters.
3. Create an empty rfc ZRFC_SendDataToXI which takes in changes as parameters
4.Create a registered program (Rfc2XmbService)TCP/IP conection(SM59) from system A to ur XI box.
5. In ZRF_handleChanges rfc call zrfc_senddatatoXI using destination(Rfc2XmbService) submit as background and if subrc = 0 commit.
6. so what we have achived so far is when ever one changes currency in system A using BAPI, the workflow is started, the first step being to call an RFC that pushes data to XI
Design in XI
1. Import ZRFC_SendDataToXI into XI
2. Import rfc from system B
3. create interface and message mapping between the above two interfaces
4. Create a communication channel to bussiness sytem A. RFC adaptor, type sender, look for registerd program , key in the registered program created in system A
So in a nutshell we have established a triggered in systemA to push data to Xi when data changes, and Xi inturn will push data to system B using the RFC in systemB.
The design i have put forward here is very generic and at a very high level. But it walks you through all the steps.
Hope its helpful .
Regards
Chilla..

** 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.

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

Siingle RFC destination for many XI scenarios

Hi,
I have 3 RFC->XI scenarios.
can i use the same RFC destination defined in SM59 in all the three RFC Communication channels? I tried using it. But one of the RFC channel is failing.
Can we use the same RFC destination in more than one RFC communication channels?
Regards,
Sharadha

HI,
If you are using the RFC adapter pls find these are the useful links
XI as RFC Destination
Using the RFC adapter (sender), how do I know which RFC is being sent?
XI as RFC Destination
Reward if needful.
Thanks,
RamuV

How to delete RFC destination during runtime

Hi Experts,
I need to delete the RFC destination (created via SM59) during runtime. Which API can I use to do so?
Thanks & Best Regards, Johnney.

Do delete different type of RFC destination at runtime , you can use these FM on the basis of its type:
1. To Read Type of RFC Destination use
                RFC_READ_DESTINATION_TYPE
2. To Delete RFC Destination
               RFC_MODIFY_ARFC_PARAMETERS
               RFC_MODIFY_HTTP_DEST_TO_EXT
               RFC_MODIFY_HTTP_DEST_TO_R3
               RFC_MODIFY_L_DESTINATION                - Read Documentation
               RFC_MODIFY_R3_DESTINATION             - Read Documentation
               RFC_MODIFY_TCPIP_DESTINATION        - Read Documentation
Regds.
Suman

RFC Destination (ABAP) to use Single Sign on

How do I configure an RFC destination to take the current user-id and connect to the RFC destination system without prompting for logon? (I do not look for a dedicated user-id pwd option - must use the current user's id)
SNC is configured, and when I doubleclick in sap logon pad, I get connected to the corresponding SAP system without the login screen. Specifying the same parameters in the SNC def (SM59 - change destination) doesn't make any difference and returns an RFC error when trying to test.
I have checked SSO links (some) on SAP help site (Do I need to configure the system in SSO2?). From portal and all it works fine. Not sure what specific config is required to connect to ABAP RFC destination to use SSO (or SNC whatever it be) to not throw the login screen.
Any help?
Thanks,

i assume you are talking about to ABAP systems.
check this link, you have to set up trust relationship between the systems.
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/22/042671488911d189490000e829fbbd/frameset.htm">Trust Relationships Between SAP Systems</a>

Unallowed RFC-XML Tag (SOAP_EINVALDOC) - Web Service using ABAP Proxy

Hi there
I am trying to consume a Web Service using ABAP Proxies. I have done the following in the system:
I configured the HTTP and HTTPS Proxy settings.
I created a package with package interfaces SAI_TOOLS and SAPPINT included under the Use Access tab.
I created the proxy classes by using the WSDL provided by the system I'm trying to interface with.
I created my HTTP destination RFC via SM59.
I configured a logical port for the proxy.
I developed the ABAP code for calling the proxy.
In the code the exception CX_AI_SYSTEM_FAULT gets raised with error message "Unallowed RFC-XML Tag (SOAP_EINVALDOC)" when I call the method for passing data to the destination system in the proxy class.
I had a look at SM21 and the following message was written in the log:
"SOAP Runtime: SOAP Runtime exception: 111 occurred in method XP_READ_TAG of class CL_SOAP_XP at position 1
SOAP Runtime: Exception message: Unallowed RFC-XML Tag (SOAP_EINVALDOC)". I also looked at SAP Note 919886 which states that it can be dumps in the system, missing configuration or the path prefix of the RFC destination that is incorrect. I cannot find any ST22 entries. The trace file looks as follows:
SAP System ID: DGH
Client: 009
User: COLESKG
System time: 072910
System date: 20070531
SAP Release: 700
Host: hd307c
Operating system: AIX
DB System: ORACLE
Program: ZUK_IPA00003
Processing State: 0
Location: Client
Transport Binding: http://schemas.xmlsoap.org/soap/http
SOAP Application: urn:sap-com:soap:runtime:application:client
SOAP Runtime Protocol: http://www.sap.com/webas/630/soap
/runtime/protocol
SOAP Protocols: <initial>
Request Message: <initial>
Response Message: <initial>
Fault: <initial>
Registry: <initial>
SOAP Roles: <initial>
Trace Level: 3
Logging Level: 2
Monitoring Level: 0
Security Profile: <initial>
WS Security Protocol: <initial>
INFO 07:29:10: SOAP LP Registry CL_SRT_LP_MAINTENANCE->CREATE_CLIENT_APPL() Try to create client application for Proxyclass:
ZES_CO_PROCESS_EMPLOYEE_BATCH LP name: DEFAULT
INFO 07:29:10: SOAP LP Registry CL_SRT_LP_MAINTENANCE->CREATE_CLIENT_APPL() Client application created
INFO 07:29:10: SOAP LP Registry CL_SRT_LP_MAINTENANCE->CREATE_CLIENT_APPL() Try to initialize client application
INFO 07:29:10: SOAP Application CL_SOAP_APPLICATION_CLIENT->IF_SOAP_APPLICATION_CS~INIT() Try to initialize application
urn:sap-com:soap:runtime:application:client
INFO 07:29:10: SOAP Application CL_SOAP_APPLICATION_CLIENT->INTERNAL_CLIENT_INIT() Create new runtime CL_SOAP_RUNTIME_CLIENT
INFO 07:29:10: SOAP Runtime CL_SOAP_RUNTIME_CLIENT->REGISTER_APPLICATION() Try to register application
INFO 07:29:10: SOAP Runtime CL_SOAP_RUNTIME_CLIENT->REGISTER_APPLICATION() Application registered
INFO 07:29:10: SOAP Application CL_SOAP_APPLICATION_CLIENT->INTERNAL_CLIENT_INIT() Read type of transport binding from
configuration
INFO 07:29:10: SOAP Application CL_SOAP_APPLICATION_CLIENT->INTERNAL_CLIENT_INIT() Create new transport binding type
http://schemas.xmlsoap.org/soap/http
INFO 07:29:10: SOAP Transport Binding CL_SOAP_TRANSPORT_BINDING_ROOT->IF_SOAP_TRANSPORT_BINDING~INIT() Try to initialize
http://schemas.xmlsoap.org/soap/http
INFO 07:29:10: SOAP Transport Binding CL_SOAP_TRANSPORT_BINDING_ROOT->IF_SOAP_TRANSPORT_BINDING~INIT() http://schemas.xmlsoap
.org/soap/http initialized
INFO 07:29:10: SOAP Transport Binding CL_SOAP_TRANSPORT_BINDING_ROOT->IF_SOAP_TRANSPORT_BINDING~REQUEST() Try to create request message
INFO 07:29:10: SOAP Transport Binding CL_SOAP_TRANSPORT_BINDING_ROOT->IF_SOAP_TRANSPORT_BINDING~REQUEST() Request message created
INFO 07:29:10: SOAP Transport Binding CL_SOAP_TRANSPORT_BINDING_ROOT->IF_SOAP_TRANSPORT_BINDING~RESPONSE() Try to create response message
INFO 07:29:10: SOAP Transport Binding CL_SOAP_TRANSPORT_BINDING_ROOT->IF_SOAP_TRANSPORT_BINDING~RESPONSE() Response message
created
INFO 07:29:10: SOAP Runtime CL_SOAP_RUNTIME_CLIENT->INIT() Try to initialize
INFO 07:29:10: SOAP Runtime CL_SOAP_RUNTIME_CLIENT->INIT() Check transport binding
INFO 07:29:10: SOAP Runtime CL_SOAP_RUNTIME_CLIENT->INIT() Create runtime protocol
INFO 07:29:10: SOAP Runtime Protocol CL_SOAP_RUNTIME_PROTOCOL->IF_SOAP_PROTOCOL~INIT() Try to initialize SOAP Runtime-intrinsic
Protocol as SENDER with Priority 5
INFO 07:29:10: SOAP Runtime Protocol CL_SOAP_RUNTIME_PROTOCOL->INIT_MODULES() Try to create trace header/part
INFO 07:29:10: SOAP Runtime Protocol CL_SOAP_RUNTIME_PROTOCOL->INIT_MODULES() Trace header/part created
INFO 07:29:10: SOAP Runtime Protocol CL_SOAP_RUNTIME_PROTOCOL->INIT_MODULES() Try to create logging header/part
INFO 07:29:10: SOAP Runtime Protocol CL_SOAP_RUNTIME_PROTOCOL->INIT_MODULES() Logging header/part created
INFO 07:29:10: SOAP Runtime Protocol CL_SOAP_RUNTIME_PROTOCOL->IF_SOAP_PROTOCOL~INIT() Protocol initialized
INFO 07:29:10: SOAP Runtime CL_SOAP_RUNTIME_CLIENT->INIT()
Initialized
INFO 07:29:10: SOAP Protocol CL_SOAP_PROTOCOL_FACTORY->CREATE()
Try to create instance for http://www.sap.com/webas/630/soap
/runtime/session/protocol::http://www.sap.com/webas/630/soap
/runtime/session/protocol/srt640_impl
INFO 07:29:10: SOAP Protocol CL_SOAP_PROTOCOL_FACTORY->CREATE()
Instance of CL_SOAP_SESSION_PROTOCOL created for http://www.sap.com/webas/630/soap/runtime/session/protocol::http://www.sap.com/webas/630/soap/runtime/session/protocol/srt640_impl
INFO 07:29:10: SOAP SESSION Protocol CL_SOAP_SESSION_PROTOCOL->IF_SOAP_PROTOCOL~INIT() Try to initialize SOAP Session Protocol
as SENDER with Priority 5
INFO 07:29:10: SOAP SESSION Protocol CL_SOAP_SESSION_PROTOCOL->IF_SOAP_PROTOCOL~INIT() Protocol initialized
INFO 07:29:10: SOAP Application CL_SOAP_APPLICATION_CLIENT_GEN->CONFIGURE_FEATURES() Try to configure features
INFO 07:29:10: SOAP HTTP Binding CL_SOAP_HTTP_TPBND_ROOT->IF_SOAP_HTTP_TRANSPORT_BINDING~SET_CLIENT_BY_DESTINATION() Try to
create ICF Client for DESTINATION = ALSB
INFO 07:29:10: SOAP HTTP Binding CL_SOAP_HTTP_TPBND_ROOT->IF_SOAP_HTTP_TRANSPORT_BINDING~SET_CLIENT_BY_DESTINATION() ICF
Client created by DESTINATION
INFO 07:29:10: SOAP HTTP Binding CL_SOAP_HTTP_TPBND_ROOT->IF_SOAP_HTTP_TRANSPORT_BINDING~SET_DESTINATION_URL_PATH() Set
DESTINATION PATH = /SapHRSmartIntegrationWeb/processes/ProcessEmployeeBatch.jpd
INFO 07:29:10: SOAP Application CL_SOAP_APPLICATION_CLIENT_GEN->CONFIGURE_FEATURES() Features configured
INFO 07:29:10: SOAP Application CL_SOAP_APPLICATION_CLIENT->IF_SOAP_APPLICATION_CS~INIT() Application urn:sap-com:soap
:runtime:application:client initialized
INFO 07:29:10: SOAP LP Registry CL_SRT_LP_MAINTENANCE->CREATE_CLIENT_APPL() Client application initialized
Trace file opened at 20070531 073030 GMT SAP-REL 700,0,95
Error in module XMLParserGetNextElement:773
Id @(#) $Id: //bas/700_REL/src/krn/rfc/xrfcpars.c#2 $
Unallowed RFC-XML Tag
Error in module XMLConverterReadTag:3061
Id @(#) $Id: //bas/700_REL/src/krn/rfc/xrfccnvrt.c#5 $
Unallowed RFC-XML Tag(24)
Error in module ab_soap:4392
Id @(#) $Id: //bas/700_REL/src/krn/rfc/abxrfccal.c#2 $
failed with return code 1
It then must be something in the config. Has anyone got any idea why this message is encountered?
Kind Regards
Gustav Coleske
Message was edited by:
Gustav Coleske

Hi,
I have the same problem as described.
Can you give me a little more information about the error you have solved in the proxy.
Thanks for help
John

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

"Unable to determine destination partition, disk or drive" when Media deployment is used

We are heavy users of MDT 2013's "media" deployments -- in fact, once we finish testing a new image build on our lab server, media is created and is the sole method we use to deploy new systems due to many limitations.
We ran into the following issue lately when using USB sticks or hard drives for our deployment media. Deployment of an OS image fails at the "Inject Drivers" stage. The hard disk inside the computer is formatted properly, but the TS fails with
the error "Unable to determine destination partition, disk or drive".
I dug into the logs, and it appears that "Inject drivers" does a check for where the \Drivers folder should be placed. The problem is that most USB hard disks and many higher-end USB sticks show up as "hard drives" rather than "removable
media" when plugged into the machine. Adding another physical disk that appears as a fixed disk with an NTFS partition apparently confuses MDT and you get this error message. I think any "ReadyBoost enabled" USB stick has to show up on the system
as a fixed disk rather than removable, so if you use these you might have this problem.
The only workaround is to explicitly specify the disk number and partition number to use when you invoke "Install Operating System." The drivers step must take this information when determining where to put the driver store.
Is there any other explanation for why this would be happening? We're stuck with media deployment for the foreseeable future, and until Microsoft fixes the problem with handling of split WIM files, we have to use NTFS formatted disks/sticks...this might
be making it harder for the MDT logic to determine where to put the OS.

MDT should be smart enough to know that it should Skip USB drives.
However if you have a USB 3 Hard DIsk (not a USB Flash Disk), that might be the problem
1. Try using only Flash Drives.
2. Try plugging the USB Hard Drive into a USB 2.0 port
3. Additionally try not to use USB Hard Drives that are *Larger* that the internal hard drive.
If you still have problems, can you copy your Bdd.log file to a public site like OneDrive and share the link?
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

RFC destination from XI ABAP engine to 4.5 B system

I tried to create an RFC destination from XI ABAP engine to 4.5 B system.
It does not work and gives an error.
Error Details DETAIL: NiIGetSockName
-Naveen.

Hi Naveen,
First of all try to ping 4.5B system from XI system (Through TELNET)... This is to ensure the connectivity and the access. The error is not a common error, i suppose, So better first we check the phisical connectivity...
Plz. confirm...
Regards,
Audy

How to call RFC in Async Mode using TCP/IP RFC Destination ?

Hi experts,
Can anybody tell me how to call an Async RFC using TCP/IP RFC Destination ?
Regards,
Umesh

Check the link
http://help.sap.com/saphelp_nw04/helpdata/en/80/09680289c751429ab3b07ad2a61c10/content.htm
It says
 For asynchronous calls, no connection to external systems is possible (TCP/IP connections in transaction SM59).
Regards,
Abhishek

How to create RFC Destination without using SM59?

Hello all:
We are troubleshooting an issue. An user created a RFC destination. He claims that he did not use SM59. We checked his access and do not have SM59 in his roles.
He configured VIRSA FireFighter. During the configuration, he created RFC destination. Document says use SM59 or contact BASIS Admin. He claims that he used a config table and he don't remember the config table name. RFC screen shows his ID as creator of the RFC.
We are trying to understand how an RFC can be created (outside of SM59) and plug the security hole in the environment.
Any insights would be appreciated.
--Anand

The FireFighter solution changes the RFC destination of the service user "on the fly" without S_TCODE checks for 'SM59'. But if I can remember correctly when looking into this, it does not create the RFC destination (in SM59) "on the fly".
> He claims that he used a config table and he don't remember the config table name.
Theoretically this is possible - a config table to define the name of the destination, and then create it if it does not exist yet (when used).
Otherwise, see SAP note 587410 and restrict (remove) his authority for the test environment (concentrate on S_DEVELOP, not S_TCODE - as you have also experienced).
Cheers,
Julius

Use of RFC destination "DEST" of type SNA/CPI-C connections

Hi ,
Please tell me the use of RFC destination "DEST" of type SNA/CPI-C connections in PI system .
Connection test for this RFC is failing with message "Error when opening RFC connection" . whether it is normal ?
Regards ,
Hanumant

Dear Hanumant Anarase,
Have you find any solution for your problem,
Because i am facing the same issue, as you mentioned above.
Regards,
Furqan

RFC Destination using ABAP / 4 driver

Similar Messages

Maybe you are looking for