Sender RFC Issue

Hi All,
I have an RFC-XI-File Scenario which is working fine in dev and qa. After moving to Pre-Prod, I see the inbound XML's do not have all the values. I debugged the program before the RFC call in R/3 and I see all the values. However when it come to XI there are only few values getting populated.
I have restarted the channels but no luck.
Please note that the scenario is working in Dev and QA and the IR objects / and ID objects are like.
Please suggest solution
Regards
Unni

However when it come to XI there are only few values getting populated.
XI (normally) wont modify the input payload (unless mapping logic is applied).....are you able to see the entire message content in the log of your Communication Channel?
Also there should not be any version conflict between the RFC in the SAP system and the RFC in XI/ PI
Regards,
Abhishek.

Similar Messages

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

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

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.

CALL_FUNCTION_REMOTE_ERROR when trying to call Sender RFC

I am trying to use the sender RFC adapter without much luck. I have written a small ABAP program to call the function - it contains the lines:
call function 'mi_rfc_check_picking'
destination 'ZXI-DEV'
When I run this, I get an error "CALL_FUNCTION_REMOTE_ERROR".
"JCO.Server could not find server function 'mi_rfc_check_picking'"
I have not been able to find any clear documentation that specifies what the function name should be set to - mi_rfc_check_picking is the name of my sender message interface as defined in XI. I have tried putting this value in upper and lower case without luck.
In component monitoring in XI, under the RFC sender I get the following error message:
- Error: 2006-08-16 12:08:17 EST: com.sap.mw.jco.JCO$Exception: (123) JCO_ERROR_FUNCTION_NOT_FOUND: JCO.Server could not find server function 'mi_rfc_check_picking'
Can anyone confirm what the RFC name should be? Or offer any other suggestions to help resolve the issue?
Regards,
Jason

Hi Jason,
Also Check if the RFC is remote enabled..
Please go through this link to know more about the same...
http://help.sap.com/saphelp_nw04/helpdata/en/f9/3f69fd11a80b4e93a5c9230bafc767/content.htm
Also just see if you have used BAPI_TRANSACTION_COMMIT.
And finally, Try checking the userid auth. for RFC destination,if it has remotes access.
To check the same, you just have to do a remote logon from SM59 transaction.
Regards,
Abhy

Sender RFC adapter Error- request was null while trying to extract it.

Hi All,
I have a scenario running in Production(PI 7.0 system) where SAP ECC sends RFC request through sender RFC adapter. The scenario was working fine but now I am getting the below error in default trace and I couldn't see any error in communication channel monitoring.
java.lang.Exception: RfcServer[BAS_ECC_RFC_Snd]1[AFSenderD] request was <null> while trying to extract it.
I have gone through the below thread and performed a full cache refresh but it didn't help :
[NULL]
I have gone through SAP note:730870 and I couldn't get any help on this error. Can you please suggest your ideas to solve this issue.
Thanks & Regards,
Laawanya

Hi Lawanya,
Check you RFC and input data , whether the RFC call is able to get the data from ECC or not.
you can test the same RFC in ECC with input data and you can check whether the RFC in ECC is return the value or not.
I gues in your case the RFC in ECC is not return any data to PI.

Sender RFC adapter - Tight coupling to an SAP client

Hi ,
We are using a sender RFC adapter to receive a RFC request from SAP , process the request in XI and then send back a response to SAP.
Our requirement is that , this request may come from different SAP clients(client 100, 130 , 200 etc). Looks like RFC adapter configured under a Business System in XI cannot listen to calls from multiple clients and works for only one client. We get dumps in SAP when invoking this RFC from other clients.
Also i hear that the same program id cannot be used in two different RFC sender adapters, meaning i have to create a different RFC destination , create a different program id for each client in SAP.
Is there a way around for this issue ?
Thanks
Saravana

Hi Saravana,
you may try a little workaround:
configure your rfc adapter only with client 100
and try invoking RFC from clients: 130 , 200
on the client 100 first (with a dummy RFC on client 100)
and then from this dummy RFC on client 100 you can start your standard RFC with your rfc adapter
don't know any other way:)
Regards,
michal

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

Sender rfc..async rfc to file scenario

Since im new to XI...Can you please give a overview of the whole scenario which meets the requirements... wrapping 1 rfc in another and then passing the final export parameters to a file using XI..
->i refered to Re: XI : RFC Response Mapping
also to the blogs 1438 and 3865.
but the things r so abstract as to how to triggger the rfcs..
Is it like calling the first rfc frm an abap pgm n calling the second one from first ...the only way?? How to achieve this?
->In what cases do we need this wrapping??
Is there any way as to just pass the export parameters of a single rfc to a file using xi.
->Dont know whr to start the scenario to work out...even the mappings are confusing...

For implementing Sender RFC: (yet to work on this)
1) We cannot use all the BAPI/RFC as is while doing an Async sender RFC.
2) We should use a wrapper around this BAPI/RFC and it should be a custom RFC again.
3) All the data that you need in XI for mapping should be passed through exporting or tables only.
4) Importing parameters should be commented.
5) Call this custom RFC in BACKGROUND TASK with DESTINATION. COMMIT WORK after calling custom RFC.
6) Create RFC destination with Program ID same as the program ID in your communication channel.
7) Import your custom RFC into repository.
8) Use the custom RFC(request not response) as interface in all your agreements and interface mapping,
message mapping.
That should be all the steps. You should get your data in receiver adapter.

Sender RFC Adapter , Sender File Adapter - Payload Compression

Sender RFC Adapter or the Sender File Adapter compress the payload of any spaces in between the tags or remove any spaces at the start and end of the payload.
We need to pass the spaces as is in the message payload to the receiving system?
Is there a way to do it in PI 7.1.

Hi Vikrant,
Preserving white spaces while reading a file from FTP
NameA.fieldContentFormatting
- Enter trim to remove all the leading and subsequent blanks for a value found. This is the default.
- Specify nothing to ensure that the value remains unaltered.
For RFC you need to check your payload to see whether spaces are coming from R/3 itself or not.
Regards
joel

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

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>

Sender RFC from Third Party System

I have a vendor who is actually communicating through RFC from third party Application to SAP R/3. Now we are trying have XI in between. Where as with minimal impact on both sides.
Solution.
1. Have the RFC made as ZRFC in XI. Let the vendor call the RFC in XI ABAP and internally make an RFC call through XI Interface to R/3 as Sync Interface. Because we need to report the information back to the system where the request initiated.
2. Have RFC INI file copied as SAP Suggests under one of the folders. Develop the regular RFC to RFC Interface via XI.
Is there any other alternatives other than the above mentioned solutions? Or out of those 2, which one will provide the best performance
Appreciate any feedback. Please advice

That's exactly what we are trying to achieve here. By Eliminating direct connection R/3, we are placing XI in between. But with the budget/timeline constraints from the Partner side, we are trying to have minimal change on the partner side. They might not change something to web service etc...
Here is the text about INI file
You can configure the non-SAP RFC client to connect to the sender communication channel in the following ways:
■ By defining the parameters PROGID, gateway-host, and gateway-service within the saprfc.ini-file using RFC-SDK.
■ By using appropriate parameters in the function RfcOpenEx.
If you use the saprfc.ini-file, the respective RFC destination has to be of type R.
All the parameter values used within the saprfc.ini-file or with the function RfcOpenEx should match the entries maintained within the corresponding sender communication channel.
Example for the saprfc.ini-file is as follows:
DEST=RFCCLIENTEXT
TYPE=R
PROGID=P106646.HKExternalClient
GWHOST=pwdf2153
GWSERV=sapgw40
Please check the following link, for the same text on RFC Sender
[Help.SAP|http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm]
Using the same Sender RFC for non-SAP System, please share any ideas

Sender RFC Adapter AND Rec. File Adapter

Hi
Workflow of my scenario is like this :
SAP R/3 ---> Sender RFC Adapter ---> XI Server -
> Rec. File Adapter -
> Legacy System
I am using Async Inbound interface for this as I dont need any response back & I just need to create file.
I am just picking some data from BAPI & creating a file on a folder in Legacy System.
Now during execution, file is getting created but I am getting dump on SAP R/3 and even when I am using Async communication, response is coming back from Legacy Business System ( service ) & giving an error " No Mapping Program Found " in sxmb_moni.
Kindly suggest how can I avoid getting response from Legacy System. Pls. take note again I am using Async Inbound Interface.
Regards
- Lalit -

Hi Lalit,
When your RFC is called from R/3 by default it would be in Sync mode. When this is in Sync mode it obviously will expect a response and where as in your scenario XI dose'nt give any response and there is no mapping for that and I think that is the reason you are getting that error.
So when your Sender RFC is triggered it will like this in ABAP
CALL Function "Function Name" <SM59 Destination>
and this is Sync call. To make it Async i should be
CALL Function "Function Name" IN BACKGROUND TASK <SM59 Destination>
Hoep this helps
Thanks,
Prakash

Sender RFC Issue

Similar Messages

Maybe you are looking for