RFC Comm. Channel question.

Hi all!
I've got a question about RFC scenario's.
This is the situation:
In a scenario "A" i use a comm. channel called RFC_Receiver, but in scenario "B" i also use this comm. channel to send data to R/3 from XI.
Scenario "A" has an integration process which called a function module in R/3 using the comm. channel.
The function module in R/3 has been edited and now has an extra export parameter (response of the module). I imported the RFC again in XI, so the new structure is known and can be used in the mapping. When using the new structure by sending a document through the integration process, we first have to set the comm. channel RFC_Receiver to INACTIVE. Then set it to ACTIVE. I've been told that this has to be done, if not it will still run with the old structure. (see question 1 below)
Now, when i transport all the changes to the production system, scenario B also will try to use RFC_Receiver. Now i have to set it to inactive and then to active (see above situation). So when i set it to inactive, i expect Scenario B to generate errors when it has to process a message. (see question 2 below)
Now my questions:
1. Do i really need to set the Comm. Channel RFC_Receiver to inactive, then activate it, set it to active and again activate it?
2. RFC_Receiver is an object used by scenario A and scenario B. When i set it to inactive for scenario A, will it also be set to inactive for scenario B? (i think it will, because it is 1 object)
Can anyone help me clear out these questions? It will me much appreciated!
Thanks in advance.
Marcel Leeraar

From tthe RFC adapter FAQ
Q 5: What's about cache memories within the RfcAdapter?
A: The RfcAdapter has a cache for the metadata of function modules. This means it caches the definition of function modules, structures and other datatypes. A separate cache is used for each communication channel. When the particular data is needed during runtime, the cache is filled from the configured RFC metadata repository. Once if a particular metadata has entered the cache, only this one is used and no lookups to the RFC metadata repository are made for this type of metadata. If the communication channel is changed within the Integration Directory and gets replicated to the appropriate Adapter Engine (see Environment -> Cache Notifications...), this metadata cache is cleared. The caches for all communication channels are cleared when the J2EE Engine is restarted, the RfcAdapter J2EE Service 'SAP XI Adapter: RFC' is restarted or a dependend J2EE Service is restarted ('SAP XI AF CPA Cache', 'SAP XI AF Messaging').
After making the change in your RFC , reason you need to deactivate and activate the RFC adapter is that the RC metadata needs to be cleared from the Cache so that the new RFC metadata is used by the RC adapter.
Regards
Bhavesh

Similar Messages

Adapter engine field blank in RFC Comm channel (Sender)

Hi Friends,
I am not getting any value in drop-down list of adapter engine in RFC adapter sender communication channel.System is allowing me to save the comm channel , system is giving me following error
No adapter engine specified
I m getting values of adapter engine when I select some other adpter like XI.
Thanx
Anand

Hi,
The RfcAdapter is implemented as a J2EE Service and thus this service has to be started and stopped. This will affect the whole RfcAdapter and can be done from the J2EE Engines Visual Administrator. When you are connected to the J2EE Engine choose the tab 'Cluster' and open the appropriate server node in the tree. Then open the 'Services' node. There you can see the entry 'SAP XI Adapter: RFC'. When you open the context menu on this entry you can start and stop the service
Regards
Chilla...

Adapter Engine drop down blank while creating Reciever RFC Comm Channel

Hi,
I am trying to create a Receiver RFC Communication Channel. But the dropdown for Adapter Engine is not showing "Integration Server" option as it shows when we create IDOC or XI Receiver Adapter communication channels.
Any help will be great.
Regards,
Shubham

Hi shubham,
this might the some error in post intallation.please revisit ur post installation steps,paricularly the adpater engine,wher u need to specify the adapters which requires the integration server.
regards
jithesh

Sender RFC comm channel - program ID

Hi all,
Short question:
I have RFC to FTP scenario.
Sender RFC channel needs a program ID.
I created a TCP/IP RFC Destination in source SAP system and specified in there the program ID i will use. However, when i try to test this connection, it throws folllowing error:
Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: program SAD_TO_DXI not registered
Error Details LOCATION: SAP-Gateway on host xxxxxx / sapgw05
Error Details DETAIL: TP SAD_TO_DXI not registered
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 6852
Error Details MODULE: gwr3cpic.c
Error Details LINE: 1694
Error Details RETURN CODE: 679
Error Details SUBRC: 0
Error Details RELEASE: 700
Error Details TIME: Wed Sep 26 17:21:55 2007
Error Details VERSION: 2
Could you please tell me how can i solve this?? and confirm this is the parameter i have to specify in the Sender CC??
Thanks in advance and kind regards,
David

hi David,
I guess the connection between R/3 and XI is not proper......
Connection between XI and R/3
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Also check the program ID
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
Also check discussion
Re: Why Program ID
regards
biplab
Use a Good Subject Line, One Question Per Posting - Award Points

Using URL Parameters with HTTP Comms Channel

Hi,
I need to build a new interface (HTTP - RFC) which will use several URL parameters. I've created a HTTP communications channel and Sender Service and this works. I'm able to define several URL Parameters by checking 'Adapter-Sepcific Message Attributes' and then 'Apply URL Parameters' then specifying the individual parameters.
This is straight forward so far but in usual SAP fashion the documentation on HTTP Comms Channels and URL Parameters is non existent. My question is how do I use these parameters once they are passed. I need to use the values as input parameters for the RFC which means I'll need to map these in the Integration Repository I can't find anything on SDN or SAP help that answers the question.
I know I could include these values in the XML payload but that would mean my 'customer' would need to amend their application and I'd rather keep things as they are.
Looking forward to your replies.
Thanks in advance.

May be this could help you to refference . .
For each process template, you can define interactive or composite form reference objects that can optionally be executed at runtime.
To be able to see and execute the reference object at runtime, you must add an appropriate runtime view.
Prerequisites
You can only attach standalone interactive forms to a process. For more information, see Interactive Form Types.
Activities
To attach an interactive form to a process:
       1.      Open the gallery and select a process template. To open its design time, choose Open
       2.      To switch to edit mode, choose (Edit).
       3.      Open the Forms tab page.
       4.      Choose Add and select the type of reference object you want to add. You can choose between Callable Object and Development Object.
Browse and select the reference object, and choose Add once again.
       5.      Repeat step 4 to add more objects.
       6.      To define parameter mapping, select an entry and choose Map Parameters. Select a parameter from the left-hand table, and then select the parameter you want to map from the right-hand table. This groups the input parameters of the form reference object to the relevant input parameters of the process.
If the process does not define input parameters, you can set default values.
       7.      When you have defined the required mappings, choose Done.
       8.      Whenever a newer version of the form reference object is available, its status on the Forms tab page changes to (Deprecated). To update the object, select it from the list and choose Update. The status changes to (Active).
Parameter mapping is preserved unless the parameters of the new object version are different. In this case, you need to define mappings again.
       9.      Finally, choose (Save).

Comm Channel and Adapters

Hi,
My Scenario is RFC-XI-JDBC. I created one Message Interface, synchronous, abstract, and did the Interface mapping.
I created sender comm channel, receiver comm channel. I configured Sender Adapter(RFC) and Receiver Adapter(JDBC).
I have a little confusion, do I need another two comm channels and another two sender(jdbc) and receiver(RFC) adapters.
Thanks for the help.

Hi Raj,
As your scenario says that you are making use of sync communication. Using the same sender and receiver channel the request and response comm is handled. While you create the outbound interface you check the option of msg interface type as sync.
So bottom line is you dont have to create two seperate channel to get the response from the JDBC adapter.
Hope this answers your question.
Regards,
Ajay

What are criterias to create Config. Scenarios and Comm Channels?

Suppose we have 10 interfaces of same kind - file to file , some of them are inbound some of them are outbound relatively to R/3.
Suppose also we have 15 File to Rfc , 5 rfc's to File .All they are interfaces communicating with external partners(that are not on our landscape)
I have few questions regarding the config in ID.
1. In the case above - what would be the criteria to create new Configuration Scenarios, how many are needed ?
2.Is it right to create Config Scenario for each Interface ?Or os it right to create all same kind if (e.g. file to file) under one Config Scenario?
3. what would be the criteria to create Communication Channels, how many are needed ?
4.Is it right approach to create 2 separate Comm channels recv/send for each separate interface?Or may be I can Reuse some communication channels from another already created interfaces - true or not?
I will appreciate your fast reply and also if you know what is the best practice..
Thanks !
Jon

Hi jon,
For the 15 File to RFC scenario u can have a Generic scenario to pick up the file and route it to the respective other scenario i.e design one common generic interface to poll the file and route it to 15 other scenario this reduces u to have onle one CC instead to have 15 communication channels and 15 receiver determinations from the file sender.
Have a look at this Blog.. <a href="/people/sravya.talanki2/blog/2005/08/16/configuring-generic-sender-file-cc-adapter Generic Sender File CC Adapter</a> By Sravya Talanki
also read thru the comments of this blog to get the clear picture...
also look at my wiki... <a href="https://wiki.sdn.sap.com/wiki/display/XI/SingleSenderFileCC4MultipleDirectories">Single Sender File CC 4 Multiple Directories</a>
Regards
San
Remember to set the thread to solved when you have received a solution there is a Way.

HTTP Comms Channel and UTL Parameters

Hi,
I need to build a new interface (HTTP - RFC) which will use several URL parameters and I have a few questions
1) In my limited experience I know that HTTP scenarios don't usually require a comms channel. Like RFC it's built into the ABAP stack. If I create a HTTP comms channel for a particular service does that mean that any interface that is part of that specific service will use my HTTP comms channel? In other words all I need to do is create a comms channel for a particular service and it will be used.
and secondly....
2) Creating the parameters in the comms channel is straightforward. I check 'Adapter-Sepcific Message Attributes' and then check 'Apply URL Parameters' then specify the individual parameters. Straight forward so far but in usual SAP fashion the documentation on HTTP Comms Channels and URL Parameters is lacking to say the least. My question is how do I map those parameters in the Integration Directory.
Looking forward to your replies.
Thanks in advance.

OK, so once I create a sender agreement then my HTTP CC will be used? That makes sense.
In regards to the second question - As I said in my posting I want to use several URL parameters. For example sending the date as part of the URL rather than the payload. These parameters are specified as part of the comms channel but mapping the parameters to the RFC must be performed in the Integration Directory. So I'd like to understand how I do this.
Thanks

Adapter engine field blank in File Comm channel (Sender)

Hi,
I am not getting any value in drop-down list of adapter engine in file adapter communication channel.System is allowing me to save the comm channel but when I am trying to create sender agreement, system is giving me following error
Unable to find an associated SLD element (source element: SAP_XIIntegrationDirectory, [CreationClassName, SAP_XIIntegrationDirectory, string, Name, directory.s01., string], target element type: SAP_XIIntegrationServer)
I m getting values of adapter engine when I select some other adpter like IDOC or RFC.
Please help...

Hi,
1) Can you check your Post Installation.
2) Look for SAP NOTES.
3) Try cache refresh
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
If you still face issue try this .
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss

PI 7.1 RFC Communication Channel not found

Hello,
We have recently upgraded to PI 7.1 and I am having a problem getting my RFC adapter to work. This is the error message:
Error when calling an adapter by using the communication channel CC_UDF_RFC_CALL_TO_PI_ABAP (Party: , Service: IS_D06, Object ID: 5873a160602e3be5866ab820596b752c) The channel with object ID 5873a160602e3be5866ab820596b752c could not be found in the Integration Server Java Cache. Check if the channel exists in the Integration Builder Directory and execute a refresh of the Java Cache
I went to SXI_CACHE and refreshed (Delta nad Complete). I can see that the CC exists in integration builder.
How can I determine what is causing this error?
Thanks,
Matt

Also check the cache notification after activating the Comm channel in ID whether cache is properly updating for the changes in the comm channel.
Menu--> Environment --> Cache Notification
If cache notification is proper thentry to refresh CPA cache using following URL and execute ur scenario.
[http://<host>:<port>/CPACache/refresh?mode=full]
Edited by: Samiullah Qureshi on May 14, 2009 8:36 AM

Sync/Async - JMS receiver comm. channel not processing

I have a Sync/Async scenario (without bpm) in PI 7.11:
RFC -> PI -> JMS
whereby the JMS receiver comm. channel does not fully process the message.
More specifically, the RFC sender comm. channel gets a message in and passes the message to the JMS channel, but that JMS channel within the RWB comm. channel log only shows the entry:
- Message processing started
The odd twist to this is that when we bring the PI server down, then back up again, (or wait a period of time, still trying to determine this period) the FIRST message attempt does successfully get processed, i.e. the first message on that JMS receiver comm. channel RWB log shows as:
- Channel successfully processed the message: 08499236-387c-11e0-b002-000025bab2c2
- Stored the correlation ID 08499236-387c-11e0-b002-000025bab2c2 of the request JMS message: ID:c3e2d840d4d8d4f24040404040404040c754dc12d8b54ec6 correponding to the XI message: 08499236-387c-11e0-b002-000025bab2c2
- Message processing started
(but then because of an issue on the target system, no response comes back, so then we'll additionally get the log entry:
- Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: no message received
Any suggestions appreciated on what I can check here to try and figure this out. Possibly because the first message eventually errors out, it is stopping the other subsequent msgs from getting processed...
When I check the audit logs of a 'success' msg vs. a not-successful msg, the success msg has an entry (and subsequent entries) of:
14.02.2011 12:50:19 Information Transform: transforming the payload ...
14.02.2011 12:50:19 Information Transform: successfully transformed
14.02.2011 12:50:19 Information ROB: entering RequestOnewayBean
14.02.2011 12:50:19 Information ROB: forwarding the request message
14.02.2011 12:50:19 Information ROB: leaving RequestOnewayBean
14.02.2011 12:50:19 Information JMS Message was forwarded to the JMS provider succesfully."
14.02.2011 12:50:19 Information XMB Message as Binary was forwarded to the SAP XI JMS service succesfully.
14.02.2011 12:50:19 Information WRB: entering WaitResponseBean
14.02.2011 12:50:19 Information WRB: retrieving the message for 08499236-387c-11e0-b002-000025bab2c2 ...
wheras the non-success msg shows only:
14.02.2011 12:55:30 Information Transform: transforming the payload ...
14.02.2011 12:55:30 Information Transform: successfully transformed
14.02.2011 12:55:30 Information ROB: entering RequestOnewayBean
14.02.2011 12:55:30 Information ROB: forwarding the request message
14.02.2011 12:55:30 Information ROB: leaving RequestOnewayBean
So, we can see that the message is not "forwarded to the JMS provider..." in the non-success case.
And also the sxi_monitor shows these messages with a status of "Log version".
Keith

Hi Siddhesh - yes that was a while back and am trying to remember the resolution. I have implemented sync/async bridges (as well as async/sync bridges) successfully, so I don't mind checking your settings, particularly I am interested in the settings within the Module tab of the JMS receiver. I can then compare to mine if you'd like. Also if you can let me know what underlying queuing system in that target system (e.g. MQSeries?) that would be great.
Regards,
Keith

No adapter registered for this channel FOR JDBC COMM CHANNEL

Hi Friends,
We installed JDBC driver(for Oracle) and it works correctly from Visual Administrator.
We have created comm channel 'jdbc_receiver'.
However, when we check in "Adapter Monitoring", it is not active (Green color) and short text says 'No adapter registered for this channel'. Where should we look further to resolve the issue ? How do we test this comm channel from XI box ?
Thanks.
Niranjan

Hi Niranjan,
How you solved the problem?
I have deployed JDBC driver (sqljdbc4.jar) according tohttp://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b4a020-4ae6-2c10-5a95-fed4ad9a4b60?QuickLink=index&… .
Driver deployed successfully and I have checked it in folder \usr\sap\xxx\DVEBMGS30\j2ee\cluster\bin\ext\com.sap.aii.adapter.lib\lib and it's found ok. But this adapter type not showing in Communication Channel only RFC and SOAP are showing there. I have restarted the server also.

Comm channel direction...

Hi,
One simple basic question..... I am using PI 7.1
Landcape ECC --> PI --> third party
If in PI Integration builder, I see a communication channel that says as follows, what does that indicate , is it reading the file from ECC appl server or is it putting the file in the server ?? what does sender and receiver mean ?
Comm channel name : xyz
comm component : third party name
adpter type: File
Sender radio button selected
Transport protocol : FTP
Message protocol: File content conversion
Adapter Engine: Central adapter engine
Source tab:
Dource directoy :/usr/sap/ecc/comm/sd/out/work/myfolder
filename: test*.xml
FTP connection paremeters set with server and port numbers and user login details given
content conversion tab:
doc name, doc namespace set and record structure set as Record, 1

Landcape ECC --> PI --> third party
comm component : third party name
Dource directoy :/usr/sap/ecc/comm/sd/out/work/myfolder
First two details seem to contradict with Source Directory path!

RFC to XI Question

Hello everyone,
I am looking to configure an RFC to XML scenario via XI, wherein I use the function module: BAPI_SALESORDER_CREATEFROMDAT2 to send data from R/3 to XI.
I understand I have to create an RFC Destination (SM59) with type - TCP/IP in SM59. However, where do I indicate that the function module to be used is BAPI_SALESORDER_CREATEFROMDAT2?
I'm told that the "registered server program" should merely correspond to the Program ID in the "RFC sender comm. channel" in the Integration Directory.
How can I trigger BAPI_SALESORDER_CREATEFROMDAT2 to send data once I create a Sales Order in R/3?
Thanks in advance!
Glenn
PS. I have loaded the RFC into the Integration Repository message mapping and configured the necessary routing rules in the Integration Directory.

Hi Glenn,
Bcoz BAPI are RFC enabled and can be triggered from VB/JAVA or any other third party S/W.
They can call from their application which will invoke the BAPI in SAP and get the req done.
For this u have to create BAPI then create a business object in SWO1 and give them
Aslo tell them how to use the BAPI reg the parameters u have used in ur BAPI as they dont know anything reg SAP.
PROCEDURE:
GOTO SWO1
then click on create button
then give the object name
then genarate the object
then GOTO SE37 and release the FM
then release the object in SWO1
then UTILITIES->ADD API methods->add
then genearate the object once agin.
after that u can see it in BAPI Tcode
go through these links
http://www.microsoft.com/technet/itshowcase/content/biztalkaipi.mspx
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/BTS_2004WP/html/d22ea1bc-de7a-440e-961a-25f83e28e141.asp
Regards,
Vinod.

Can't save new comm channels after upgrade to PI 711

I've been provided a recently upgraded PI system, 7.11 from 7.1.
After creating a new comm channel and adapter type, and trying to save, the following error is displayed:
"The chosen Adapter Engine has version 710 but the chosen Adapter Metadata has version 711. Use Adapter Metadata with the same or with a lower version as the Adapter Engine instead"
At the beginning I couldn't even see the File/RFC/Idoc/... adapter type of SWCV 7.11. I could only select the adapter types of SWCV 7.10. so I imported the ESR content for SWC SAP_BASIS 7.11. Now when selecting the adapter type I have both versions, 7.10 and 7.11.
I suspect some post upgrade operation was skipped, but I'm not sure.
Thanks

Dear Jorge,
I do have the same issue.
My PI 7.11 system is sending its data, RZ70 for ABAP and SLD_DATA_Supplier for JAVA - to our SAP Solution Manager.
SAP Solution Manager's SLD runs on SAP NetWeaver 7.01.
PI's SLD runs on SAP NetWeaver 7.11.
What do you mean by local SLD ?
Do you mean that my PI system must pointed to its own SLD, running on SAP NW 7.11 ?
Thanks
SAP NetWeaverAdmin

RFC Comm. Channel question.

Similar Messages

Maybe you are looking for