TDMS auto-generated RFC Destinations cleanup

Hi Experts,
We have performed the deletion per note 1030483 - TDMS Deletion/reorganization of
transfer packages for completed and incomplete packages.
But we noticed the RFC destinations auto-generated by TDMS still remained and pilling up in the systems.
Would like to get some expert opinions whether we should delete or keep these RFC destinations?
Thank you.
BR,
Bee Huang

Hi,
If you are not using the packages9old) any more , you can delete the generated RFCs for the old packages as well.
Reagrds,
Sandeep

Similar Messages

How to change Auto-generated web service's URL

Hi,
is it possible to change/edit the auto-generated url of a web services created with the wizard in SE80 transaction?
Example:
Now the wizard generates a URL as following:
http://<host name>:8080/sap/bc/srt/wsdl/bndg_4BC67655E5155680E10000000A7B0410/wsdl11/allinone/standard/document?sap-client=001
where the alfa-numeric code 4BC67655E5155680E10000000A7B0410 changes every time I create the service. at the same time and for the reason above, I have to change the LOGICAL DESTINATION with "visual administrator" application to consume the service in SAP Netweaver environment.
Thanks in advance.
Luca

Hi Luca,
Please refer the below link . it is described that URLs and its Namespaces . Please check whether its useful.
[http://help.sap.com/saphelp_nw70/helpdata/EN/8c/780741375cf16fe10000000a1550b0/frameset.htm] .

RFC destination error in posting 3rd party payment in 4.7 FI system

Hi,
We are running in to a problem when we are processing a payment via transaction F110S in our R/3 4.7 system for Financials. We are integrating our Financial system with ECC6.0 for HCM. We receive 3rd party invoice from HCM successfully via ALE and post it in 4.7 system. When we try to process payment against this invoice, apparently 4.7 system is trying to communicate with ECC 6.0 system and issuing an error and the payment processing gets cancelled. It generates a clearing document with out a check.
The error says "An RFC destination could not be specified for the logical system HD1CLNT014
    Message no. B1550
Diagnosis
    An RFC destination should be specified for the logical system
    HD1CLNT014. This could not be done in this case. HD1CLNT014 is not your
    local logical system and this system is not included in the relevant
    Customizing tables.
Procedure
    Check:
        -   RFC destination
           -Port definition
         -oubound partner profile of message type SYNCH for this logical system
We checked our configuration for all Logical system and RFC destination and everything seems fine.
Any help in this regard is appreciated.
Thanks
Kesav

Hi David,
Did you check below is set-up correctly.
- Use transaction SM59 to create an RFC destinations for the remote system.
- Use transaction BD54 to create the logical system.
- Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
Also, check entries in TBLSYSDEST is filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
Thanks,
Ameet

RFC destination for synchronous communication (message type SYNCH)

Hi experts,
I am trying to configuare ALE settings.waht i did is
My sending & receiving systems are one server with different clients.By using SALE transaction
1.crated logical systems.(LS_800 &LR_810)
2.Assigned those to clients.
3.Created RFC destination
4. Created modelview assign sending & receiving
systems and message type.saved it.
4.generated Partner profile.Here i am getting below problem
Target system LR_810
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LR_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Target system LS_800
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LS_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Regards;
Upender.

Hi Shital;
Thanks for your replay;
Still am getting the Same Error;
Thanks;
Upender.

RFC destination of receiver system

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

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

System crash RFC destination

Hi,
When creating projects it fails with the messages:-
1) System crash RFC destination , Call TMW_VERSION_TEST: User SAPSYS has no RFC authorization for function group TMW_TRACKING .
2) System crash RFC destination , Call TMW_VERSION_TEST: Name or password is incorrect. Please re-enter.
3) RFC destination error SM_PRDCLNT000_READ: RFC task PRD:000:TMW_GET_FULL_LIST already open.
It is my understanding that 1 and 2 are related. The question I have is: How do I assign auhtorisation for SAPSYS to the function group TWM_TRACKING?
Regards

Hi Ferrandi,
See if these notes are relevant to your scenario:
Note 896042 - RFC access from satellite systems generates dump
Note 920805 - Correction of the FM TMW_VERSION_TEST in Note 804198
Also Which user do you use to generate the RFC`s??? Check the authorization for that user to generate RFC`s.　Ｔｈｅ　ａｕｔｈ　ｏｂｊｅｃｔ　S_RFCACL and S_RFC which is not a part of SAP_ALL profile should be assigned to the user.
Hope this is helpful.
Regards,
P. Kumaravel.
Ps: Award points for helpful answers.

No rfc destination is defined in SAP Global Trade Services

when doing MB1C transaction the above mentioned error is displayed(errror: No rfc destination is defined in SAP Global Trade
Services ).doing MB1C transaction through movement type 561 the system is accepted,but through MT 501 when we are doing
the process, the system will generate the aove mentioned error.pls give the correct solution.
regards
Maran

Re: Getting dump MESSAGE_TYPE_X while posting in MIGO

RFC destination TMW

I am configuring Solution Manager 7.0, When I am trying to generate the RFC connections it gives me the following errors.
1.RFC destination SM_SMDCLNT001_READ creation error. RFC destination many have errors.
2.RFC destination SM_SMDCLNT001_READ generation error
3.RFC destination SM_SMDCLNT001_TMW creation error. RFC destination may have errors
4.RFC destination SM_destination SM_SMDCLNT001_TMW generation error
5.No RFC destination assigned for read access for client 001.
But Read, back, trusted, login connections when tested for connection are playing good. How do I fix the above issues.
Is it something related to the Scheduling of Background jobs which we do during the configuration?
Thank you Druva

Hi ,
This error is purly due to user access. when you are trying to create these RFCs, Solman will connect to that satellite system logon screen where you have to enter your username and password. RFC users will be created by the user which you are entering in the logon screen.
Use the appropriate user in the satellite system and also check the authorization.
If you are using CUA then i would suggest you to create the RFC users in the satellite and in solman use the option Exsisting user and password while creating RFCs.
Feel free to revert back
Regards
Naveen

NO RFC Destination for BAPI's

Hi,
I am working on ALE for Activity allocation. I am using 3 methods in my distribution model. I need to transfer data from ECC 6.0 source system to R/3 4.7.
BUS6010 Method POST & CHECK
BUS2072 Method FINDDETAILS
I am using the Program RHINLV00_LSO to transfer data.
When i execute this report it's throwing an error
" NO RFC Destination for 2 BAPI's".
An RFC Destination is created in SM59 to link the two systems and i have distributed the distribution model to R/3 4.7.
The Function modules are marked as Remote enabled function modules.
Regards,
Ramesh K.

Hi,
After creating the distribution model with 3 methods in ECC 6.0 (source system). Generated Partner profile automatically from BD64. Then distributed the distribution model to the other system i.e., SAP R/3 4.7 successfully. Then created partner profile from that system automatically.
Port, partner profiles,outbound parameters, inbound parameters were created successfully.
Thanks
Ramesh

SRM-SUS RFC Destinations for matching of user data.

Hi,
A customizing question...
I get SRM and SUS in separated boxes... SRM is with all the SAP landscape (R/3, XI, MDM, etc..) and SUS in the DMZ to allow vendors to reach the web site....
So, there's an activity to setup the connection to replicate the bidders created in SUS to SRM...
the IMG activity is: SPRO-> SRM -> SUS -> Technical settings -> Define RFC destinations fot matching of user data.
There are 4 parameters to input:
Destination -> (SRDCLNT400).
System name -> (SRM)
FM BPID -> (empty)
Role -> (SAP_EC_BBP_BIDDER)
So, my question is: What's the name of the FM that should input here FM BPID?
I think that it is a FM in SRM side, but i don't know how to find it, is there any documentation about this RFC?
All your replies will be appreciated and rewarded if useful...
Regards,
Gerardo.

Nishant,
BBP_SUS_BUPA_REGID_CHECK is the FM in charge to check out the string generated by the system for a vendor that was invited to register tu SUS via email... so i don't think that it will work..
Let me redefine my question cuz maybe it is not so clear...
When you invite a vendor, he will register and will get an administrator user, with which he will create more users (bidders) to review and post quotes.... But, since the bid engine is independent from SUS (at SRM side) the SUS user will need to be replicated at SRM with same user name and password... Then when they go to the BID option in SUS menu a new browser window will prompt for login...
If you are running SUS in a different box from SRM, there's an IMG activity to setup the RFC name to replicate the user names with bidder role.. This is the step where i'm stuck, cuz in the documentation there isn't any references to this RFC...
So, if you have something that will help me, please reply, i will reward useful answers...
Gerardo.

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

ShellCreation -RFC destinations

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

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

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

Error generating RFC connections when using the wizard in SMSY

We are using the wizard in smsy to generate the rfc destinations but the error
Error create rfc destination back and also no read destination assigned for read access.
The user has s_rfcacl assigned on both sattelite and solman system and
we have tried deleting and recreating (by rerunning the wizard) rfc
destinations. We have also tried to manually create the rfc
destination. Any help appreciated.

Hi,
The problem still outstanding is with rfc connection SM_<SID>CLNT<CLIENT>_TRUSTED in the Solman system. The error message is [No authorization to log on as a trusted system (Trusted RC=1).]
The following roles/authorisations are allocated to the user
S_RFC
S_RFCACL
S_TABU_CLI
S_TABU_RFC
S_TABU_SHOW
S_TCODE
S_USER_GRP
and SAP_ALL.
I have regenerated the roles, etc. Deleted and recreated the trust, using wizard and manually still error. The connection from the sattelite system to the Solman works fine. Please assist further.

Monitor RFC Destinations

Hi guys,
Couldn't find a way simply monitor RFC destinations with CCMS monitor. Specifically, I've RFC destination type T (http)
can't find a way to monitor it.
Please advice,
Dimitry

Hi
        Availability can be implemented using the RFC availability check for specific RFC destinations.
        Monitoring of specific and critical RFC destinations can be done by using the standard CCMS MTE
        class CCMS_RFCDest_Availability_Col
        Using the methods described above, alerts can be generated in the CCMS monitoring transactions
As specified above note 1069130 will help you in achieving it.
Thanks
Amit

TDMS auto-generated RFC Destinations cleanup

Similar Messages

Maybe you are looking for