TCode GRMG - RFC dest - Type G - to SLD

Hi,
I am following blog
/people/sap.user72/blog/2005/12/05/xi-grmg-customizing-for-xi-ccms-heartbeat-monitoring-part-ii
I have downloaded the xml template from note 634771.
While customizing the transaction GRMG, I have created an RFC destination of type G, to connect to SLD.
Connection test of the above RFC destination, gives the
Test Result : Bad Request
Response Body :
<b>400 Bad Request</b>
<b>HTTP method GET is not supported by this URL</b>
Can someone help me with this.
Thanks,
-Naveen.

Tuhin Kumar Oza,
Cud u plz go through the following link,
http://help.sap.com/saphelp_nw2004s/helpdata/en/a1/9cdb4064da712ae10000000a155106/content.htm
see the table under the head procedure.
See the Path Prefix entry against System Landscape Directory.
Reg,
-Naveen

Similar Messages

Connect Webmethods Flowservoce using RFC Dest Type G

Hello Friends,
For my scenario i need to send Material Master Idoc to Webmethods, the idoc is received by a flow service written in Webmethods developer.
now I am strucked at RFC destination i am trying to create TYPE G connection, here what value i need to enter for "Path prefix " .
We want to connect directly using RFC Dest with out using any adapters.
appreciate any help (Information / blogs.....)
Regards
Satish

Tuhin Kumar Oza,
Cud u plz go through the following link,
http://help.sap.com/saphelp_nw2004s/helpdata/en/a1/9cdb4064da712ae10000000a155106/content.htm
see the table under the head procedure.
See the Path Prefix entry against System Landscape Directory.
Reg,
-Naveen

RFC_SENDER_XI : RFC Dest Error

Hi All
I am configuring the RFC Destination on the ECC6 of typer TCP/IP to communicate RFC to XI, when i create the RFC destination RFC_SENDER_XI of type TCP/IP i am getting error
Error Details     SAP gateway connection failed. Is SAP gateway started?                    / CPIC
Error Details     ERROR: SAP gateway connection failed. Is SAP gateway started?
Error Details     LOCATION: SAP-Server eccserv_EC6_01 on host eccserv (wp 0)
I have configured the RFC Sender Adapter and i am using the same PID of RFC Sender in my RFC Dest, the RFC destnation is throwing error when i mention the host name of ECC in Gateway host.
Any clue where is the problem, how should i activate the gateway host on ECC, is there any such thing to activate gateway host also when i run TCode SMGW on ECC i am not able to see any active connectiions there.

Now i am getting the error on the RFC_SNDR Adapter
Error Details:
Error: 2007-08-07 11:02:26 GMT+05:30: com.sap.aii.af.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService 'ECC_SERVER', toParty '', toService '', interface 'ZMK_TEST_RFC', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_RFC_SNDR' (channelId 389e1dc5421a32b5a336160fb15d71eb)
I have done the cache refersh still getting same error

RFC Destination type for IDOC to FILE

Hi,
wat is the RFC Destination type for IDOC to FILE ?
jeff

hi,
u shud create rfc dest tye: R/3 connections...that is type 3.
refer this:
R/3 side settings
1. SM 59 (RFC destinations)
Create a RFC destination pointing to the XI server. The connection type : R/3 connection. The target host: the XI server.
2. WE 21 (Ports in IDOC processing)
Create a transactional port. Give the RFC destination created in this.
3. BD 54
Create a logical system.
4. WE 20 (Partner Profiles)
a. Create a new partner profile under partner type LS.
b. Assign the message type in outbound parameters.
c. Open the message type (Dbl click) and configure the receiver port to the port created.
XI side settings.
1. SM59 (RFC destination)
Configure the RFC destination pointing to the R/3 system.
2. IDX1 (Port maintenance in IDOC Adapter)
Create a port and provide the RFC destination.
[reward if helpful]
regards,
latika.

Regd. Creation of Port and RFC dest in PI

Hi Experts,
I have two scenarios 1. file to IDOC and 2. IDOC to file.
for first , i need to connect to ECC for posting IDOC. in sap side they have created port ,partner profile etc.
in PI sides i created an RFC destination(sm59) ,given generic name, i have created port(idx1) and mentioned the partener num say(SAP123) ant type (LS). Loaded the meta data in idx2. i am able to post IDOC in sap.
for the second case,i am supposed to receive idoc from sap.
do i need to create another port and rfc destination ? or simply adding the metadata in the prev created port will help.
Actually i tried creating another RFC dest and port and was trying to assign same partner num (SAP123) and type (LS)
while loading the metadata i get an error saying 'basic type of the IDOC is unknown'.
from SAP side the IDOC status is green , saying idoc is dispatched to the target port.But in Trn. SE58, there is error show.
Is this something wrong in PI or SAP ?
Please help me with the steps to be followed with suggested naming conventions if any.
Best regards,
Srinivas

Hi,
Port type shouldbe SAP SYSID ...it is important that you create the port with this naming convention as the name is very important to be followed...
Try to create the port name with the above mentioned..and give a try...
Also post the error generated in the SM58 ...
HTH
Rajesh

Change of RFC dest during Create BP via DSWP

Dear all,
I'm creating Business Partner via Tcode DSWP. Where in the screen "Create Business partner" got to know there are Satellite system being attached on the tree in left hand.
My questions:
1) may i know how can i perform the config if i want to edit/delete/add the system?
2) How can i assign the RFC dest accordingly each of the system?
Please comment.
Thanks in advance.

My Answers:
1.) The creation of Business Partners along with their associated system, system identification number, and user ID is maintained in Transaction BP.
In Transaction BP select the button "Person" to create. Go to the Identification Tab. In the Identification Numbers area you will need to add entries for every system/client combination you want to create messages for.
In the IDType column Choose CRM001
In the Identification Number column maintain the entries as follows:
<System> <Installation Number> <client> <UserID>
For example: PSM 0005063405 300 RGODFREY
So, if you want to edit/delete/add systems that are mapped to business partners you may do that here.
2.) RFCs are required to be generated before creating business partners in BP. This is performed in transaction SM59. Once the RFS are created and generated in SM59, you are free to add/edit/delete the systems according business partner.
Award Points.

Rfc dest

hi ,
1. if i am doing only a file to idoc scenario do i need a rfc dest from SAP to XI
if yes why??
2. if i am doing a idoc to file scenario do i neeed rfc dest and port from XI to SAP
if yes why??

for file to idoc check:
http://wiki.sdn.sap.com/wiki/display/XI/FileToIDOC
for sender IDOC check:
https://wiki.sdn.sap.com/wiki/display/XI/SAPR3IdocsToXI--Steps+Summarized
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660?quicklink=index&overridelayout=true

RFC Destination Type G too fast

Hi All,
I have an RFC Destination (Type G) that is pointing to another XI system. We use that to send messages directly from XI to XI. However, when there is heavy load,we get a lot of failures in the source XI System. Messages go eventually after many retry attempts.
Is there any way that i can slow this down, so that the messages queue up in the Source system and flow slowly towards the target. We can do this in a Type 3 RFC destination by reducing the number of connections in Transaction SMQS. Any such options for Type G?
Thanks,
Varun

Hi Liang,
Thanks for your response.
We are using the XI adapter. Also, to clarify, this is a connection between 2 separate XI Systems.
Thanks,
Varun

RFC Destination type RFC Receiver Adapter?

Hi,
What is the RFC destination type for Sender RFC Adapter?
and what is the need a Program ID for sender Adpter.
What is the RFC destination type for Receiver RFC Adapter?
Regards
Gopi

When we use the RFC Adapter?
SAP systems up to and including SAP Release 4.6 are not able to exchange data by using XML messages and http. The only way you can connect such systems to the Integration Server directly is by using the RFC adapter (or the IDoc adapter).
You require the sender adapter if you want to use the Integration Engine to process RFCs. The RFC adapter converts the incoming RFC data to XML message format (RFC XML) so that it can be processed by the Integration Engine.
You require the receiver adapter if the determined receiver system expects the data from the Integration Engine to arrive in RFC format. In this case, the Integration Engine must transfer the received XML message (RFC XML) to the RFC adapter. The RFC adapter converts the RFC XML message to a valid RFC call and executes the call.
The following three scenarios are possible when using the RFC adapter and the Integration Engine:
    1) SAP R/3 to SAP NetWeaver Application Server
    2) SAP NetWeaver Application Server to SAP R/3
    3) SAP R/3 to SAP R/3
When we use ABAP Proxy ?
SAP systems based on Web AS 6.40 and higher are able to exchange data by using messages and HTTP. These systems can use ABAP proxies to connect to the Integration Server.
To connect the platform-independent message interfaces, which are stored in the Integration Repository, to the Integration Server, use the ABAP proxy interface.
Please Reward the points if it's helpful...
Regards,
Ramana.

RFC destination types

When do we use RFC destination Type T versus Type 3?
While creating RFC destination Type T, the program ID, blogs says we should use "Registered server program" and can give any free text. I tried that but says there is no registered server program called XXX on system. So, i'm really confused here.
my understanding is for IDOCs you need Type 3, and for RFC you need Type T. Is that true or we can use any type with these?
Thanks,
Anika

Hi Anika,
i think this links could be useful:
http://help.sap.com/saphelp_47x200/helpdata/en/22/04262b488911d189490000e829fbbd/frameset.htm
Differences in the RFC destination types
You're right, for Idoc you have to use type 3 and for RFC you have to select a type T destination entering a program ID.
Let's make an example.
Suppose you have defined an RFC destination RFC_X with program id PID_X on ECC.
On XI you have created an RFC sender adapter and you have specified ECC as the sender and PID_X as the program ID.
When from ECC an RFC is called using destination RFC_X then the sapgateway looks for a receiver registered with the program id PID_X, it finds your RFC adapter and sends the call to XI.
Hope it helps.
Kind Regards,
Sergio

Remote comparison RFC Dest

Hi,
my system is solution manager 7.1 the last stack
ST-PI 05
when i use in CDMC i get the results i want to try - remote comparison,
when i click on the remote comparison i need to choose RFC dest,
i get a list of rfc that i dont understand from where the solution manager gets it,
also when i try to choose RFC i get the Error
"RFC destination different from destination system"
I find the note 1636163 but it's not compatible my system my ST-PI
Best regards
Naor Shalom
Edited by: Naor Shalom on Feb 2, 2012 9:27 AM

Gyula,
I believe it is all controlled in SM59 where you can set the login id and password as trusted. Whe you call this function module remotely from your program, the logical destination system set in SM59 probably not set as trusted.

TCP/IP RFC dest entry not displaying in we21

Hi Experts,
i have created an RFC Destination in sm59 with connection as TCP/IP. In we21 when i try to assign the RFC dest to the tRFC port, the dest entry was not displayed. No RFC dest belongs to TCP/IP connection was displayed there.
Please give your input for the cause of the issue.
Thanks,
Siva

Go back to SM59 and see whether you save the new connection and its displayed there ?
Thanks
Prince Jose

Naming of RFC Dest SAP R3- XI- Partner

Hello,
I want to send an Idoc via XI to different external partners. I know how to setup the RFC dest from R3 to XI and so on...
The question is the following:
How do you name your RFC Destinations in R3 system?
One for each external (the final receiver of the Idoc) or is it recommended to use the XI system as destination for all
How to handle ALEAUDIT messages...seems the better way to name the final partner...
what are the suggestions...
Thanks for your ideas,
bye
jo

Hi,
If you are going to be doing an IDOC to IDOC then by naming the partner as your R3 systems then you do not need to manipulate your Idoc's control record in XI.
If you did this wrt to XI, then the IDOC control record will have R3 as sender partner name and XI as receiver partner name... When XI send s the IDOC, the control record will need to be maniuplated with XI as the Sender Partner and R3 as the receiver partner.
I hope this clears the concept. I would recommend naming it( paretner profile ) with respect to the actual partners
The port / RFC destiation can be named with respect to XI and used in the partnerinside the partner profile.
Regards,
Bhavesh

RFC Dest. Parameters for ALIEN Device Integration?

hi,
    I am trying to Integrate Alien Device to SAP AII.
In RFC dest. ALE_OUT
   HOST: ip address
   service/port : 23
   path : /
but I am getting an " ICM_HTTP_CONNECTION_FAILED" error.
thanks,
arul.

hi,
    I am trying to Integrate Alien Device to SAP AII.
In RFC dest. ALE_OUT
   HOST: ip address
   service/port : 23
   path : /
but I am getting an " ICM_HTTP_CONNECTION_FAILED" error.
thanks,
arul.

RFC dest . parameter Problem

Hi Friends,
I am getting a problem when i restore the Source system.
No RFC dest.parameters maintained for the
Warehouse in source system BQACLNT100
When i am asking my basis team to checck for the connection in the source system they are telling that connection is working fine
Please help me to solve this problem
Regards
Raju

hi Raju,
it seems authorization problem,
oss note 126066, old one but may relevant, it's said ALE user (ALEREMOTE) is missing an authorization in the source system - BQACLNT100. what's your r/3 version.
you may have higher version, but still try to check authorization area.
Cause and prerequisites
The error message can have two causes:
1. The user ALEREMOTE is missing an authorization in the source system
    (only for systems as of Release 4.0B)
2. The field "Application server" carries out a conversion to upper
    case in the dialog "automatic connect" (only for source systems on a
    UNIX operating system)
Solution
Solution for 1:
Join the profile S_BI-WX_RFC in the source system to the authorization:
Object:        S_ADMI_FCD
Authorization: S_WF_RFCDEST
Value:         NADM

TCode GRMG - RFC dest - Type G - to SLD

Similar Messages

Maybe you are looking for