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

Similar Messages

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

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

Problem with sender RFC adapter

Hi All
I have created one RFC adapter for which i have created wrong business system and all then i have deleted that and i have created on more RFC adapter but when i am testing my scenario its taking the old one which i have deleted from the Integration directory. I have refreshed the cache using sxi_cache and also in RWB. But still i m getting the same error...
Could you please tell me how to resolve this error

Hi
Yes i have configured RFC as sender communication channel. I have deleted the old one including the business system. but still in adapter monitoring i m getting the error "com.sap.aii.af.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/'Whirlpool_BS1'/'RFC_Source_CC', lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'QN9#800' returned party/service of ''/'QN9')"
but i have deleted the whirlpool_bs1 business system.
Why still i m getting this error.
Thanks & Regards
SUN

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

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 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 with sender agreement in rfc

My scenary is RFC -> XI -> FILE.
I created one message interface with atribute asyncronous and output message the rfc.
I created one interface mapping and message mapping
In integration directory I created one chanel of comunication,the receiver determination, the interface determination, the receiver agreement and the sender agreement. In the sender agreement in interface I put the same name of message interface and then I activated all.
When i execute the rfc i have one dump. This dump is "senderAgreement not found: lookup of binding via CPA-cache". But i declarated and activated the sender agreement.
Somebody knows the problem.
Thank's for all.

Hi Antonio,
A few things that you should know:
1) You need not create a message interface for RFC, as RFC iself is an interface.
2) You need to create one inbound message interface for file message.
3) You will need two message mapping, one for request message and one for response message in case yours is a synchronous scenario. But only one message mapping (request) in case of asynchronous scenario.
4)One interface mapping both for sync and async scenario.
In Integration Directory:
1) 2 communication channels: sender RFC and receiver File.
2) 1 Receiver determination, interface determination and sender aggrement.
Regards,
Ashish

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

Problem while sending IDOC to File Senario

Hi Experts
 I am having problem while sending the Idoc from SAP R/3 to File
 I have done all the setting in SAP as well in XI but while pushing IDOC
 I am getting error in the transaction sm58 in SAP R/3
" The service for the client 300(My SAP R/3 client) is not present in Integration
Directory"
I can any one explain me what to done on this....all the connections are fine
Waiting for Response
Adv points and thanx
Rakesh

Reason and Prerequisites
You send IDocs from system ABC to the exchange infrastructure (XI) of system XIZ, and error messages are issued in system ABC (Transaction SM58) for the IDOC_INBOUND_ASYNCHRONOUS function module.
This note proposes solutions for the following error messages:
a) No service for system SAPABC client 123 in the integration directory
b) Transaction IDX1: Port SAPABC, client 123, RFC destination
c) ::000
d) NO_EXEC_PERMISSION: "USER" "Business_System"
e) IDoc adapter inbound: Error error ...
Solution
a) Error message: No service for system SAPABC client 123 in the integration directory
Solution:
You send IDocs from system ABC to XI. In the control record of the IDoc, the SNDPOR field contains the value "SAPABC". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service):
Business system
Activities in the System Landscape Directory (SLD)(Create technical system):
Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
SLD (Business system):
You can now explicitly assign a business system to this client.
For more details, refer to the SLD documentation.
Activities in system ABC (self-registration in the SLD):
Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
In system ABC, you can check your configuration with TransactionSLDCHECK.
Activities in Integration Directory (import business system from SLD):
You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
Business service
Activities in the Integration Builder directory:
You want to create a service without party that is not part of your system infrastructure and is therefore not maintained in the SLD.
In the Integration Builder directory, you will find the "Business-Services" under Services Without Party. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Activate the change list in Integration Directory.
In system ABC, you can restart the incorrect entry from Transaction SM58 .
b) Error message: Transaction IDX1: Port SAPABC, client 123, RFC destination
Solution:
The Integration Server tries to load the IDoc metadata from the sending system. The IDoc schemas from the Integration Repository cannot be used because they are release-dependent.
The sending system is determined by the value of the "SNDPOR" field from the IDoc control record (for example, "SAPABC").
Activities in the central XI system:
In Transaction IDX1, you can assign an RFC destination to the sending system (for example, "SAPABC"). This must be created beforehand in Transaction SM59.
Note that the IDoc metadata is cross-client data. In Transaction IDX1, only one entry must be maintained for each system. Only the lowest client is used by the runtime for Idoc metadata retrieval with RFC.
Ensure that only SAPABC and not "SAPABC_123" is entered in the port name.
c) Error message: "::000"
Solution:
This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC.
There may be several different reasons for the failure of the metadata import, the error is not transferred in full by tRFC completely, and this results in the error message above.
User cannot log onto sending system
User/password/client is not correct or the user is logged due to too many failed logons.
Activities in sender system ABC:
Transaction SM21 contains entries for failed logons.
Activities in the central XI system:
Determine the sending port from the IDoc control record of the IDoc. If the ID of the sending system has the value "ABC", the value of the sending port is "SAPABC". You will find the RFC destination used for the "SAPABC" sending port with the lowest client in Transaction IDX1. In Transaction SM59, you will find the RFC destination containing the maintained logon data .
User does not have the required authorizations
Activities in the sender system ABC:
In Transaction SM21, you will find entries relating to authorization problems and more exact details.
Contact your system administrator and, if necessary, assign the user the required roles in user administration.
IDoctyp/Cimtyp cannot be loaded
Activities in sender system ABC:
In the sender system, you can check your IDoc types in Transaction WE30 (IDoc type editor) Take note not only of the errors, but also of the warnings.
The most common errors are:
- IDoc type or segments not released
- Segments that no longer exist are listed in the IDoc type
- Data elements that do not exist in the DDIC are assigned to fields
in the segment.
Contact your system administrator and correct these errors in the IDoc type.
d) Error message: NO_EXEC_PERMISSION: "User" "Business_System"
Solution:
You created a list of users in the directory who are authorized to use the "Business_System". The user in the error message is not on the list.
Alternatively, the same error is used if you have created a sender agreement with a channel of the IDoc type for the "Business_System" and the interface used. The user in the error message is not contained in the list of all authorized users defined there.
e) Error message: IDoc adapter inbound: Error error
Solution:
You send IDocs to the central XI system, where they are received by the IDoc adapter. The IDocs are converted into IDoc XML, and a corresponding XI message is generated and transferred to the XI Runtime Engine. The Engine tries to read its own business system from the "Exchange Profile". If the Exchange Profile is currently unavailable, the message is not processed and it is returned to the sending system with an error message.
Regard's
Prabhakar.....

Problem with Send and Receive Emal In SAP System

Hi gurus!
I have a following quote:
Dear !
I have a problem with send and receive email in SAP system following :
I want to test send and receive email in local network at my company. I
had two server
Server 1 : I setup Exchange Mail Server 2007 with domain controller is
fes.com
Server 2 : I setup SAP ERP ECC 6.0
On Server 1 : I created 2 account ( u1Afes.com and u2Afes.com ) and then I tested send and receive email between u1 and u2 in local network through Microsoft Outlook 2007 -> OK
and then
On Server 2: I had configured send and receive email on SAP system
through tcode SBWP, SCOT and SOST as Note 455140 - "Configuration of
e-mail, fax, paging or SMS using SMTP"
for example :
I logged in SAP system with user Basis01 (with email u1Afes.com ) -> then,using tcode SBWP -> new message -> send to u2Afes.com with Internet Mail type and then status message with green light -> sending ok
and then I have used Microsoft Outlook 2007, I logged with account u2 ->check email -> Ok. I saw message which send from u1
Finally, My problem is how can receive mail in SAP system without using Microsoft Outlook
For example:
Login system SAP with Basis01 account (with u1Afes.com ) -> tcode SBWP ->New Message -> send to u2Afes.com
and then
Login system SAP with Basis02 account (with u2Afes.com ) -> tcode ??? ->
To receive email from Basis01 (with u1Afes.com )
Please help me now
Thanks
I replace "@" with "A" because of banning email of this forum.
This quote is about sending email in local network. And we can't receive any email from the outside email address. Addition if I wanna send email to internal email in Internet (we've just tried with email address in local network) What should I config in SAP and Exchange ?
By the way, Is SAP Server IP added to Relay Agent for sending or receiving mail ?
Regards
An NLP
Edited by: An NLP on Apr 6, 2010 7:03 PM

Hi,
This problem is a classic problem of mail routing via Exchange. Exchange like most mail servers use the domain part of the email address as a means to route mails. So I will make an assumption that your main company mail addrss is "User @ fes.com".
So when you send a mail to the "User @ fes.com mail" address the mail is delivered to your Outlook mail address as this is the default route for company.
(Q) So how do you get your Exchange server to relay the mail into the sending SAP system?
(A) The easiest way would be to setup and unique mail domain for your SAP system. I always recommend "user @ client.sid.company.com" which in your case would be "u1 @ 100.PRD.fes.com". You can then instruct Exchange to send any emails addressed to 100.PRD.fes.com domain to your SAP system. Also using this format of address you can configure multiple mail connections into multiple SAP systems.
(A) Another answer would be to enter the "Full" email address (LOcal and Domain part of address) into the routing rule for Exchange e.g. "U1 @ fes.com" so that all emails addressed to this user will be delivered into SAP. However this method requires a lot of Admin as you will have to update Exchange with ALL email address that need to receive emails. Also if your corporate mail address is "U1 @ fes.com" then all mails will be forwarded to SAP.
I would definitely NOT recommend this method but the decision is up to you.
P.S. The IP address of the SAP system is entered into the mail header of the email. This is standard practice in SMTP relay. You can suppress this header in Exchange
Hope this helps
Michael

Problem with sending and receiving e-mail through exchange [GMail]

Hello I have problem with sending and receiving e-mail.
all is well set, username and password are correct, the server set m.google.com. verification of data is about like stepping into a post and want to check the post office gives me an error message: Can not Get Mail. The connection to the server has failed
I have this problem on my two iPhone

http://www.zdnet.com/google-drops-exchange-activesync-support-for-free-email-acc ounts-7000008836/

Problem in Sender RFC

Similar Messages

Maybe you are looking for