Sender RFC-Problem in SM58

Hi all,
Currently I am working on RFC synchronous call with out using BMP.
Here we have developed two asynchronous RFC call to achieve the above requirement.
Here are the details,
1. A call from FILE-XI-RFC (Receiver), for sending the selection criteria
2. Another call from (Sender) RFC-XI-FILE for sending the response back.
Here I am going to call 2 RFCs to get the response back. Here when I am working with the scenario (2) i.e., sender RFC, I have done all the design and configuration part of it.
And when am trying to test this sender rfc from a sample ABAP report (with COMMIT WORK) the RFC gets executed without any error but when I check in SM58 all the back ground tasks gets queued and are not getting processed further.
Can anyone please help me out? Is it a configuration problem in XI or in ABAP.
Please help me. Its very urgent for me.
Thanks in advance,
-kanth.

Hi,
did you try to push the entries in SM58 -> F6 ?
do you see any error ?
also check out my blog:
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
to see if your RFC to XI is correct - you can test it from sm59
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Similar Messages

Sender RFC problem

Hi,
I defined a Sender RFC to build RFC-XI-Others scenario, accoring to the document here, I create a sender RFC communication channel with the host and service(sapgw00) of R/3 system, and specified a program ID, then I created a TCP/IP destination in R/3 with the sames host, server, and program id, but when I did the test with SM59, it says: program RFCTEST not registered / CPI-C error CM_ALLOCATE_FAILURE_RETRY.
What's wrong with my setting?
Thanks a lot!
Best Regards
Yuedong

Dear All,
Thanks for your replies, I solved the problem!
Next, I got the following error in R/3
call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:
In XI, I saw the error as:
HTTP response contains status code 401 with the description Unauthorized Error when sending by HTTP (error code: 401, error text: Unauthorized)
And I also has the problem:
Unable to notify integration runtime (ABAP) of data changes
http connection to "http://gdsapxi:8000/sap/xi/cache?sap-client=000" returns the status code "401" in response
They seems more difficult for me, could you please provide me the comments.
Thanks a lot!!!
Best Regards
Yuedong

Problem in Sender RFC adapter

Hi all,
Our scenarion is like this
RFC -> XI -> File
When we are calling the RFC ( inside a program ) from the client we are getitng a shortdump with the error ...
'JCO.Server could not find server function 'STOCK_ENQUIRY_OUT'
any idea where is the exact problem '?
regards
Goutam

Have these basic checks;
1. Import the RFC and activate the same in XI.
2. Configuring of RFC adapter - /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
3. Troubleshooting - /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

Problem in Sender RFC

Dear XI Expert,
I have completed configuration part of Sender RFC scenario. In this scenario, when I execute RFC in Source SAP system, message gets routed through XI and then it is converted to file. This file is placed on a file system.
The inbound message interface is asynchronous mode.
The problem is 'After placing the file on File system, it is travelling in the reverse direction and expected mapping program between inbound message type and outbound message type.
In message monitoring it showing error with ID 'NO MAPPING_PROGRAM_FOUND' with Type to be 'Synchronous'.
1. sender service --> xi -->receiver service
2. receiver service --> xi --> sender service.
I don't want the 2nd step and want to configure 'Asynchronous' Sender RFC.
Can anybody help me in configuring 'Asynchronous' Sender RFC?
Regards,
Suraj Kumar

> Dear XI Expert,
>
> I have completed configuration part of Sender RFC
> scenario. In this scenario, when I execute RFC in
> Source SAP system, message gets routed through XI and
> then it is converted to file. This file is placed on
> a file system.
Hi suraj,
i am not able to configure Sender RFC in XI which would take RFC calls from my R/3 SAP system.
The Technical System & business system that i have created for my R/3 are of type Web As ABAP ( Is this the right option ?)
I basically get error saying Program Id not registered, what might be the reason

Problems with sender RFC from R/3 4.6D

Hi all,
I have configured a sender RFC channel on XI cluster. Immediately after channel activation everything looks fine on backend system (R/3 4.6D):
But after some time (e.g. one hour) the connection somehow stops working.
The u201CTest connectionu201D says u201CProgram ID not registered u2026 u201D and also XI hosts is not listed in u201Clogged on clientsu201D any more.
By restarting the Sender RFC from Communication channel monitor the communication is reestablished. But after an hour it breaks down again.
The strange thing is that this problem occurs only when RFC sender channel is configured on XI cluster with two nodes (our production XI on MSCA). If the same is configured on a stand alone XI (which is our development system) the connection is working fine all the time.
Also the problem happens only when connecting XI cluster with R/3 4.6 D system. When the same connection is established with ERP 5.0 or ECC 6.0 it is working fine.
Setting the property initalRfcClientConnextCheck to false didnu2019t help.
Thanks for helping.
Janos

transaction SMGW(gateway monitor) and choose menu option 'Goto --> Logged on clients'.
make sure that the there is an entry in the program id is same as program id in the RFC sender channel...if not try making a change in the RCF channel and activating again
Edited by: Tarang Shah on Feb 8, 2010 6:48 PM

Connection Issue R/3 and sender RFC

Iam using RFC sender in my scenario. I have created an RFC destination in R/3 with the details Program ID, GatewayHost, Service. Maintained the same details in RFC sender communication channel of XI. After activating my communication channel I tested my RFC destination R/3. It was succesful.
But these days we are facing the problem with that. It says ' Program Id not registered'. We used to get this error whenever either of the system(R/3, XI) goes down. that time i used to go n activate my Comm. channel the connection would be established once again.
Please let me know why iam facing this error also let me know the steps to resolve it.
Even I tried michel's blog on sender RFC....

Hi,
even we applied all the SAP notes what Naveen has suggested in his notes.But still we are facing this issue.
Do we need to check the version of R/3 and XI.Our R/3 system is 4.7e
Please suggest what to do...

Displaced content from sender RFC in payload - PI 7.0

Hello,
we have a strange behaviour here.
After implementing a scenario with HTTP->PI->RFC
which works fine transporting a structure to an R/3, we wanted implement another scenario RFC->PI->HTTP (RFC is async).
Problem when testing it:
The RFC hands over a structure which contains in the first field a order number (so leading zeros are cut).
The cutting of the zeros results in a displacing of the rest of all fields. So filling the payload PI is in some trouble and adds an error code #... in some fields.
This is why we identified the problem, because the error codes run into error during mapping.
We reimported the RFC more than once, changing the structure to be sure that we can se a successful update of the RFC structure in the repository. Everything fine, but the error is still the same.
Now we convert on the R/3 side the order no. field:
Instead of leading zeros we replaced them with '9' ´s.
Then we correct this in mapping.
But this is not a solution!
Is there anybody who had the same effect on his XI/PI using sender RFC?
If you can offer a solution for that..... would be great!
Best regards
Dirk

Hello,
this is another idea but would do the same as our '9'-solution. It would solve the specific issue but will not remove the problem itself.
We had a hint from somebody in our company internal forum:
"If you had used a custom RFC pls make use of conversion routines for the order no field. in a std rfc this would have been handeled implicitly."
Will discuss this with the developer and come back.
We got the answer:
On R/3 side there is a customer table which provides the data. There is conversion routine ALPHA already added to several fields. But only field "orderno" is resulting in trouble. We do now a move to a workarea based on a new defined structure instead of moving the select result based on the table structure to the RFC. In the structure we defined order no. as a simple CHAR field w/o any conversion behind.
So now it is working!
regards
Dirk
Edited by: Dirk Meinhard on Feb 20, 2008 6:28 PM

Sender RFC Scenario Error:Payload Is Missing

I am facing an issue in 'RFC2JDBC' scenario which is mentioned below:
here our scenario is 'RFC2JDBC'.here our 'RFC' is having 2 fields in tables parameter
i.e. empno & empname.
the results of the 'RFC' is coming as:
Personnel Number Employee Name
00000100 Rasmiraj
00000200 Tanmay
00000300 Kanhu
00000400 Debabrata
00000500 shantanu
i am triggering the 'rtfc' through a program.
when i am triggering the 'RFC',in monitor of PI it's coming as sucessful.however in the payload one of the field value is missing i.e. employee name.(same also updating in the legacy database)
in the payload it's appearing as:
[ <?xml version="1.0" encoding="UTF-8" ?>
- <rfc:ZSAM_SEND_RFC_PI xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <EMP_DTLS>
- <item>
<EMPNO>00000100</EMPNO>
<EMPNAME />
</item>
- <item>
<EMPNO>00000200</EMPNO>
<EMPNAME />
</item>
- <item>
<EMPNO>00000300</EMPNO>
<EMPNAME />
</item>
- <item>
<EMPNO>00000400</EMPNO>
<EMPNAME>a</EMPNAME>
</item>
- <item>
<EMPNO>00000500</EMPNO>
<EMPNAME />
</item>
</EMP_DTLS>
</rfc:ZSAM_SEND_RFC_PI> ]
please,suggest.(here,we are using sender 'RFC' communication channel & an 'RFC'destination of type 'T'(with parameter registered server program,gateway host,gateway service)

Hi rasmiraj tripathy,
I am also facing the same problem (Sender or Payload is missing) while integrating R3 to B1 using IDOC. When I resend IDOC, it capture by B1iSN but doesn't work, it gives me error. When I look into xml document, it is found that there is no receiver payload.
My R3 system is non-unicode and it is difficult to change it to unicode as it requires updation.
Can you please confirm that this error is coming due to Non-Unicode, and can be resolved by setting it to Unicode.
Note: There is no double definition of any object.

Sender RFC Adapter Issue

Hi ,
I am using the following scenarion (SAP ECC)Sender RFC>PI 7.1->Receiver JDBC(ThirdParty).
The issue is whenever the the ECC system is down and is up again , the RFC sender messages are getting struck in SM58(tRFC queue).What I manually do is , go the RFC Sender communication channel in PI and reactivate it again, by making a small change in the description of the communication channel.
So, my question is , whether there is a automatical ways to handel this issue.
Any other suggestions would be highly appreciated.
Thanks,
Venu

There is no standard way to perform this automatically. I think restart of ECC is not a frequent practice in any business, therefore ideally you should add this as one of the post processing procedures after ECC restart.
Technically, there is possibility of creating a scenario which can run through a job on ECC running once after each restart. This can call webservice in PI to fetch communication channel information and reactivate it. Not a solution I would recommend.
Regards,
Prateek

R/3 to XI manually IDOC sending and problem:

R/3 to XI manually IDOC sending and problem:
I sent IDOC using we19 transaction from R/3 system. After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
I check XI (sxmb_moni) but there is nomessage there.
Problem 1: I don't want R/3 ask me UID and password for XI access
Problem 2: I want to see message in XI (sxmb_moni)
Thanks

Hi Cemil,
>>>>After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
check the RFC destination from R3 to XI (SM59)
you will find the right one from your port (We21)
you can also check step by step procedures
for IDOC - XI in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Sender RFC error

Hi guys,
I'm doing an RFC to File async scenario just as mentioned in the blog
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
and i have done the configurations also from the blog
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Now when i execute my report to call the bapi with the rfc destination of my XI server, i'm getting error in sm58 of R/3 as Bean Z_BAPINAME not found. I'm not getting any messages in to XI also..
Please help me on this guys
Thanks
Varun

When i'm creating RFC destination in R/3 which gateway host and gateway service should i enter??
values from R/3 should be entered.
These you can find in transaction smgw, in menu Go To> Parameters> display
here you will get values for gateway host and gateway service of R/3
you should create RFC dest of type TCP/IP, Give a program ID .. it could be anything. This program ID you will have to provide in RFC adapter. Activate the adapter
Then Try to activate RFC dest at R/3.
For more refer
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

Sender RFC adapter High volume messaging

Hi,
This question is related to this thread:RFC connection problem
ERP system is sending through 1 RFC dest. (program ID) 20 requests in a minute. And PI starts to hang. ERP is not able tp sent the messages and after a while the request sent from ERP starts to get cancelled. This is a synchonous scenario. How can I handle such a high volume through 1 sender RFC adapter?

Hello
You can monitor the load on RFC adapter queues/threadsin the RWB
-> Component Monitoring
-> Adatper Engine XIP
-> Engine Status
-> Additional Data
See note #791655 Documentation of the XI Messaging System Service Properties, for an explaination of the queues.
To increase the number of threads/queues, see the blog:
1) /people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
2) /people/kenny.scott/blog/2008/12/05/xipi-file-and-jdbc-receiver-adapter-performance-and-availability-improvements - this shows how to prevent a problem on one RFC channel blocking other RFC channels that you may be using.
Also, ensure note #937159 XI Adapter Engine is stuck, has been applied to help overall system performance.
Regards
Mark

Sender RFC Adapter only processes first message

Hi there,
we have a R/3 - XI - 3rd party scenario, where the R/3 - XI communication will be established through a RFC.
The RFC destination was properly configured in SM59 in R/3 and also was the XI's sender RFC adapter, with the same program ID.
We called the RFC in R/3 Abap code and the message succesfully arrived at XI (it could be found in SXMB_MONI). However, any other call from R/3 would not result in a message arriving at XI (no new entry in SXMB_MONI nor in Message Monitoring, at RWB). New messages only appear again if we set the status of the adapter to inactive and then active again. Then the message arrives, but again, only the first one.
Can anyone help with this?
Is there any misconfiguration in XI or RFC Destination?
Or is it the abap calling that should be processed in another way?
Thanks in advance,
Henrique.

Hi,
>>>Or is it the abap calling that should be processed in another way?
the important thing is the commit work
which must be done after call function
and you can only have one call function
before the commit work
do you see any other errors in SM58?
>>>Is there any misconfiguration in XI or RFC Destination?
Or is it the abap calling that should be processed in another way?
one or the other - no doubt about that
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Sender rfc advanced mode options

Hi Guys,
I am getting the error message saying that "looking for alternative service identifiers CPA cache failed" for the sender RFC adapter.
I have the sender BS with proper logical system name. when i debug the function module on the sender sap system it gives this error.
When i uncheck the option verify sender system in the sender RFC CC, then it gives different error saying unable to identify the BS name in the CPA cache.
I did the cache refresh and still i am not getting the data from sap. I have a scheduled job on the sap side and it dosent go the C status. can anybody suggest me whether i need to uncheck this or not
Thanks in advance
srini

Hi Srinivas !!
have a look , may be helpful
getting error in RFC sender adapter
for RFC Sender " Is it must i need to write ABAP code " ?
Problem in Sender RFC
Rfc sender problem(sap r/3 -se37) 'alternativeServiceIdentifier: party/serv
Thanks !!!!

RFC Error in SM58 Commit fault

My scenario is RFC to XI to FILE.
I made RFC destination in SM59
and configure xi according to
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
The connection test in SM59 is succeeded.
I would like to execute BAPI, so wrote following..
CALL FUNCTION 'BAPI_CUSTOMER_GETLIST'
 IN BACKGROUND TASK
 DESTINATION 'BAPI_XI_001'
 <<< parameters >>>
 COMMIT WORK.
BUT in SM58, I got error
'Commit fault: com.sap.aii.af.rfc.afcommunication.
RfcAFWException: alterna '.
Any ideas?
Best regards.

Thank you very much for your information.
I checked Q&A19 of SAP NOTE 730870
and configured XI again.
Then I got a different error...
' program BAPI_CUSTOMER_GETLIST not registered / CPI
C-CALL: 'ThSAPECMINIT'# '
I have already checked the spelling of BAPI's name.
Have you saw this error??

Sender RFC-Problem in SM58

Similar Messages

Maybe you are looking for