RFC ADAPTER destination hangs
To All
I am working on a XI 7.0 system SP5 for netweaver 2004s and am having problems with the RFC adapter.
Steps as follows:-
1.Configure SM59 tcp ip destination on r/3(4.6C) sender system using Xi system host and gateway service
2. step 2 - configure communication channel on my scenario in Integration directory. Activate channel
3. Send Asynchronous message via prgram from R/3 sender
this delivers successfully to BW target ssytem via asynchronous RFC
My problem is when I repeat steps 3 to send more my rfc destination fails with the following in the trace log:-
Trace file opened at 20060303 160158 WST, REL 46D,0,1984, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Transaction program not registered
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Transaction program not registered
DEST =ZSCEN2_XI
HOST =%%RFCSERVER%%
PROG =ZBWIP24_19
GWHOST =ux0800
GWSERV =sapgw53
If I repeat setps 1 to 3 above with a new transaction program it will again work but only once.
Any help would be greatly appreciated and I will award points.
Regards
Liz Porter
PS the adaptor monitor periodically gives the following message:-
Sender Channel 'RFC_INDE4' for Party '', Service 'ERP_WATERCORP_SAPR3_D' (Internal Name 'RfcServer[RFC_INDE4]')
Server data: {jco.server.gwhost=ux0800, jco.server.progid=ZBWIP24_19, jco.server.gwserv=sapgw53, jco.server.unicode=0}
Repository data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=100, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=portere0, jco.client.sysnr=81, jco.client.ashost=sapdev}
Current pool size: 1, max pool size : 50
RFC_HISTORY
- Error: 2006-03-03 16:49:27 WST:
RfcException:
message: CPIC-CALL: SAP_CMACCPTP3
no SAP ErrInfo available
Return code: RFC_SYS_EXCEPTION(3)
error group: 102
key: RFC_ERROR_COMMUNICATION
To All
The call from to the RFC destination is attempted as tRFC
see below:-
PARAMETERS:P_TPLNR LIKE IFLOT-TPLNR,
P_DESTN LIKE TRFCQOUT-DEST DEFAULT 'ZSCEN2_XI'.
CALL FUNCTION 'ZBWIP_FUNCTIONAL_LOCN_OUT'
IN BACKGROUND TASK
DESTINATION P_DESTN
TABLES
FUNCT_LOC_MAIN = T_TABLE.
IF SY-SUBRC = 0.
COMMIT WORK.
WRITE:/ 'So far so good check XI'.
ELSE.
WRITE:/ 'Error ', SY-SUBRC.
ENDIF.
The SM59 parameters on R/3 4.6C as set as
Connection type T TCP/IP connection
Activation Type: registration
Program ID ZBWIP24_28
Gateway:-
Type T TCP/IP connection
Gateway host ux0800
Gateway service sapgw53
and finally tRFC:-
Connection attempts up to task 2
Time betw. 2 tries [mins] 10
In the XI integration directory:-
Adapter type RFc sender
Application Server(gateway) ux0800
Application service(gateway) sapgw53
Program id ZBWIP24_28
Initial Connections 1
Maximum connections 50
Advanced Mode Maximum reconnection delay 3
A bit more information from our XI system. In SMGW on XI our program shows as "connected" and on drill-down shows status receive data/send. If however we configure a SM59 TCP-IP connection on XI to our XI gateway(ie connect to myself) I get the same CPIC message about 677 timeout for registered program.
Regards
Liz
Similar Messages
-
RFC Adapter (Destination Test)
Hello,
I made an RFC Destination with with the program ID Rfc2XmbService. But when i want to test the connection ja have this result.
"Program Rfc2XmbService no registered". What does it means?
Thanks a lot,
Enrique.It means that the program Rfc2XmbService is not registered. You can register the program in J2EE administration. THis is something that that BASIS team can help with.
- Ravi -
RFC Adaptive Model,JCO destinations error
HI,
I created the tutorial application to get Flight List using RFC adaptive model.
I created the JCO destinations in web dynpro content administrator after configuring the SLD (after many problems though ).
Our Server is Web AS 6.4 ABAP + JAVA ,but no R/3 modules installed.
WD_FLIGHTLIST_MODELDATA_DEST-type application--single server connection
WD_FLIGHTLIST_RFC_METADATA_DEST-type Dictionary-load balanced
The JCo destinations status shows green.
The test for WD_FLIGHTLIST_MODELDATA_DEST is succesful but the test for WD_FLIGHTLIST_RFC_METADATA_DEST fails with the error:[code]
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=nwserver GROUP=PUBLIC R3NAME=NWS MSSERV=sapmsNWS PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR Group PUBLIC not found TIME Thu Nov 10 18:24:23 2005 RELEASE 640 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 3515 DETAIL LgIGroup COUNTER 2 [/code]
The ping fails and if i test it again,i get another error
[code]com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=nwserver GROUP=PUBLIC R3NAME=NWS MSSERV=sapmsNWS PCS=1 ERROR Group PUBLIC not found TIME Thu Nov 10 18:29:13 2005 RELEASE 640 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 3515 DETAIL LgIGroup COUNTER 1 [/code]
What is wrong?Any more steps required?
If i try to edit it,the type is still the same-Application with single connection.
How can i change it?Do i need to change it to type Dictionary in the first place? How to proceed.
Please guide.
Regards,
Siddhartha
Message was edited by: Siddhartha Jain
Message was edited by: Siddhartha Jainhi Siddhartha,
You have to configure PUBLIC group using SMLG transaction
check these links out
http://help.sap.com/saphelp_nw04/helpdata/en/28/1c623c44696069e10000000a11405a/content.htm
hope this helps you
Regards
Rohit -
Configuring receiver RFC adapter to use RFC destination
Hello,
I have been doing some digging, but I can't find a solid answer on how to configuring a receiver RFC adapter to use an existing RFC destination to call a 4/6C R/3 backend system... Our scenario is to WS --> SOAP --> RFC which is up and running in production just fine on NW 7.0, SP12.
I ask this question because we, as a company, do not like to maintain passwords in multiple systems. That is necessary when we use the receiver RFC adapter now since SNC is a distant pipe dream for us and we would like to use an existing RFC destination that is set up to call the backend system using a logon ticket.
I checked the relevant links I could find below, but I can not resolve the answer from them. Has anyone set this up successfully? This link (RFC Destination type RFC Receiver Adapter?) mentions it briefly, but it does not go into any length on how to set it up.
Thanks!
John
http://help.sap.com/saphelp_srm40/helpdata/fr/33/c6e63b60c25767e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
Re: Asynchronous RFC callHi John !!
I suggest you to create a new user, without dialog access in your ECC system to be used exclusively by the XI system to access ECC. And then, always use this user in all RFC receiver adapter communication channels.
Regards,
Matias. -
Hi all,
I am trying file->xi->rfc adapter scenario.
My scenario is employee information is written to flat file n will be kept on ftp server.THe file adapter will pickup the file and sends it to rfc adapter through pipeline service.
This is going well. The problem is the data is not being updated into receiving sap system.
in SXMB_MONI transaction the messages are successully processed . But there are no messges in rfc adapter when i gone through idx5 transaction???
Any one have idea??
Thanks in advance.
Rgds,
Ram Srisxmb_moni only shows the status of the integration engine's processing, not the result of what happened in the rfc call. First, you can check if the adapter framework successfully passed the message to the destination system (not on moni, thru RWB)
as far as did the rfc succeed - it's as difficult as always with internal processing. We did a lot of testing by debugging modules on the destination side (manually putting in the data as the adapter would've to step thru & see where the message is "lost") - have not yet found a better way, sorry. It's not so much a problem with XI, just in general the difficulty to debug rfc's -
Error while calling RFC adapter(FILE-XI-RFC scenario)
Hi,
I am trying for FILE-XI-RFC scenario. I am getting the following error. I have checked in message monitoring. The error is coming while calling the RFC adapter. Can any body tell what problem is this?
Regards,
Dhana
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.f23.sofd00001530a</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.u7a.us4296</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.f23.sofd00001530a</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>Hi,
I did SLD check.
The status says 'Summary: Connection to SLD works correctly'.
But it fails while checking the access to XI profile.
Here is the status
Summary: Connection to SLD works correctly
Now checking access to the XI Profile
Properties of RFC destination LCRSAPRFC
RFC host:
%%RFCSERVER%%
program id: LCRSAPRFC_DZ1
gateway host:
gateway service:
Testing the RFC connection to the SLD java client...
RFC ping returned exception with message:
/ CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679#Transaction program not registere -
RFC adapter in XI 3.0 not working properly with BAPI in R/3 4.6C
Here is the scenario.
An XML file is received from our customer. This file contains purchase order information that is used to create a sales order in our SAP 4.6C system. Once the sales order is created an acknowledgement is generated and this is returned back to our customer in an XML format. This scenario is working perfectly fine in our XI 2.0 system but is not working properly in our XI 3.0 test environment. Our custom function module in R/3 is a wrapper function that uses a standard SAP BAPI to create the sales order. Part of the function module does use the statement
call function 'BAPI_TRANSACTION_COMMIT'
The last thing the BAPI does is call another function module that using an RFC destination that will return and order acknowledgement.
Here is what happens within XI and our SAP system.
The XML file is received and mapped to our imported RFC. The RFC adapter is called and the information is passed onto SAP where our customer function module executed. The sales order is created within SAP without any problems and the second function module is called which references an RFC destination assigned to our XI 3.0 system. The information is sent back to XI and an appropriate file is created for our customer. All seems to be working properly except that when the original RFC is sent from XI to SAP, SAP creates a short dump stating
"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:" Then it is put back into the que where 5 minutes later it executes again and trys to recreate the sales order in SAP. (again, this same function module executing from XI 2.0 works fine)
I believe I have everything configured properly because the SAP side is being executed and I am successfully passing information back from SAP to XI. However the original function module in SAP is failing with the above error message. It appears that the original function module cannot communicate back with XI. I have had SAP looking at this issue and they have not been successful yet in solving this problem.
Any ideas.
Thanks,
Jim d'HulstHi,
I think the problem is with the send back of acknowledgement to XI. Does the DeliveryException state something about the sender agreement? I guess you are using a statement like below:
CALL FUNCTION 'ZABCD'
destination <tcp/ip destination>
exporting
input = ack.
In that case, check whether the TCP/IP destination is working fine. Also, to be able to exchange message, the structure of the Function Module ZABCD needs to be identified as the sender in XI Configuration (Integration Directory).
Also, check your config with the blog mentioned below:
<a href="/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit">/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit</a>
Regards,
Amitabha -
RFC Sender problem between 46D and RFC adapter
Hi,
I have this simple integration scenario where I want to send data to a archiving system;
SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
SAP side ***
A Z-program using a Z func. like;
CALL FUNCTION 'ZSD_DCF_SEND_TAG'
IN BACKGROUND TASK
DESTINATION 'XISYSTEM_TRFC_DCF'
EXPORTING
pt_filing_info = gt_filing.
COMMIT WORK AND WAIT.
XI side ***
Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
The problem in quality ***
When sending just 1 msg, everything is just fine, message received and delivered to MQ.
When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
RFC_HISTORY
- Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
- OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
It seems to me that the RFC adapter is kind of confused about the sender..
I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
- The SLD config. for bus.system Q93 is ok -
- The bus.system in ID is showing correct vaues for
Adapter Specific Identifiers (SID Q93, client 505)
- Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
- It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
- It doesn't matter if I increase initial conn, max conn.
I have also tried to use qRFC instead, but with the same result.
Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
best regards
TorsteinHi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
<i>Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".</i>
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek -
RFC to XML-RFC Parsing issue in RFC Adapter as Sender
Hi all,
I tried to use RFC adapter as a sender. The scenario I am trying to achieve is R3 -> RFC Adapter Sender --> BPM --> RFC Adapter Receiver --> SAP Auto-ID system.
The reason to use two RFC adapter and BPM is to log the request message if the RFC call fails. Everything works as expected, except the RFC Adapter Sender.
The RFC I am calling has an input table. The input data I use works fine if I call it via SE37 or remotely from another SAP system. However, if I call it via RFC adapter, when XI parses the data into RFC-XML format, the input data is all messed up.
DATA: BEGIN OF ID_STR,
ID_VERSION(8) TYPE C,
ID(96) TYPE C,
ELEMENT_NAME(50) TYPE C,
ELEMENT_VALUE(128) TYPE C,
END OF ID_STR.
DATA: it_id LIKE TABLE OF ID_STR,
ls_id LIKE ID_STR.
ls_id-ID_VERSION = 'EPC_1.30'.
ls_id-ID = '30340242206DC3C00000000A'.
ls_id-element_name = 'BATCH_ID'.
ls_id-element_value = 'BATCH001'.
APPEND ls_id TO it_id.
CALL FUNCTION '/AIN/UI_MOBILE_MSG_SEND'
IN BACKGROUND TASK
DESTINATION 'RFC_UPDATEAII'
EXPORTING
IV_BUSINESS_PROCESS = '09'
IV_COMMAND = 'DO'
IV_ACTION_TYPE = 'APL2'
IV_PRT_ID = '31140242200000000F000000'
IV_DEVGRP_EXTID = 'MOBILE'
TABLES
IT_ID = it_id
commit work.
And the parsed RFC-XML message is:
<?xml version="1.0" encoding="UTF-8" ?>
<rfc:_-AIN_-UI_MOBILE_MSG_SEND
xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<IV_ACTION_TYPE>APL2</IV_ACTION_TYPE>
<IV_BTD_EXTID />
<IV_BTD_TYPE />
<IV_BUSINESS_PROCESS>09</IV_BUSINESS_PROCESS>
<IV_COMMAND>DO</IV_COMMAND>
<IV_DEVGRP_EXTID>MOBILE</IV_DEVGRP_EXTID>
<IV_LOC_EXTID />
<IV_LOC_TYPE />
<IV_PRT_ID>31140242200000000F000000</IV_PRT_ID>
<IV_PRT_ID_VERSION />
<IV_REASON_CODE />
<IV_UNAME/>
<ET_RETURN />
<IT_ID>
<item>
<ID_VERSION>EPC_1.30</ID_VERSION>
<ID>206DC3C00000000A BATCH_ID</ID>
<ELEMENT_NAME />
<ELEMENT_VALUE />
</item>
</IT_ID>
</rfc:_-AIN_-UI_MOBILE_MSG_SEND>
You can see the data in the table is all wrong, it should be:
<IT_ID>
<item>
<ID_VERSION>EPC_1.30</ID_VERSION>
<ID>30340242206DC3C00000000A</ID>
<ELEMENT_NAME>BATCH_ID</ELEMENT_NAME>
<ELEMENT_VALUE>BATCH001</ELEMENT_VALUE>
</item>
</IT_ID>
The calling system is a 4.6C non-unicode system, and the destination system is a unicode system (this does not matter since the first part of the integration is between R3 and XI). There is no config found on R3 side to specify non-unicode because it is a rather old system. In XI RFC Adapter config, I checked non-unicode checkbox (I also tested it with this unchecked, but still the same issue).
Have any of you seen this problem and how you resolve it?
Thanks a lot for your help!
Regards,
HartHi Hart
long time no seen - hope you remember me
>The reason to use two RFC adapter and BPM is to log the request message if the RFC call fails
there is an easy way (guess max 3-4 hours) to solve all of your issues
and get rid of a BPM
use IDOC - XI - ABAP Proxy
then you will have IDOC and ABAP Proxy that always log the message on both ends (and you can restart ABAP proxies easily in AII - and every AII supports ABAP proxies) + you get rid of a BPM as it's not necessary as far as I understand (as it's asyn communication right?)
maybe you can go this way and IDOCs always work...
good luck,
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ -
Sender RFC Adapter AND Rec. File Adapter
Hi
Workflow of my scenario is like this :
<b>SAP R/3 ---> Sender RFC Adapter ---> XI Server -
> Rec. File Adapter -
> Legacy System</b>
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 " <i>No Mapping Program Found</i> " 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 Adapter-- XI-- File Receiver Adapter ?
Dear Expert,
we are on PI 7.0 & R/3 system 4.7E WAS < 6.20. We have a scenario where in there are some huge downloads are required from R/3 to FTP File Location. For such scenarios Normally Poxy is suggested but Due to WAs Version limitation we cannot use Proxy. The other alternative is to use SENDER RFc adapter using RFC destination with XI. we have configured the RFC destination it is working fine.
I am able to receive the message also in XI. But whenever i am running this RFC in R/3 it is giving me the shot dump as follows. :
<b>call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:</b>
The File is also getting written to the destination properly. But in XI also i get the following error.
<b> <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>http://Test/Zbilldwd ZBILLDWD_FILE_IM</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Interface mapping http://Test/Zbilldwd ZBILLDWD_FILE_IM does not exist in runtime cache</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error></b>
What could be the reason of this.? As well i am geting 3 error messages in XI.
I have defined this interface as Inbound / Async Message interface with input message as output file structure. ( Is this configuration is OKAY ?)
pl. help me to solve this error.
Regards,
UmeshHI,
Check your configuration from the message it states that it can not find out the mapping program.
Check the configuration Receiver and interface determination whether you are using the same which is designed in repository.
Thanks and Regards,
Chirag Gohil -
Sender RFC Adapter - Data to be sent from R/3
I am working on a scenario where I have to send data from an RFC-enabled function module from R/3 to a file server via XI. The entire scenario is asynchronous.
Sender: RFC Adapter
Receiver: File Adapter
I have done all design and the configuration. Both communication channels are working. I have the RFC destination also set up correctly in R/3.
However, when I run my ABAP program where the RFC-enabled function module is called, I get a shortdump with the message <b>"senderAgreement not found: lookup of binding via CPA-cache failed for".</b>
Plus: " The error occurred during an RFC call to another system."
Could someone kidly help?Hi,
Follow these steps :
1. import the ECC_ Server into ID if not done
2. Refresh Cache : Tcode SXI_CACHE
3. Please check for Sender agreement config
4. Check out the parameters when R/3 calls back XI, it passes the SYS-ID and client number and checks the same in the Integration Configuration Under Business System Service-> Adapter Specific Identifiers. The R/3 System ID and the client Number
Also check out these blogs..
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
regards
Aashish Sinha
PS : Reward points if helpful -
Hi experts!
I am developing a RFC to File scenario on PI 7.1 EHP1 and ECC 6.0 which is synchronous. Following the Help page Setting Up an RFC Destination for the RFC Adapter I created two destinations. The fist one is a TCP/IP, name RFCDE1COMPANY2, program id BAPI_COMPANY_GETLIST and corresponding gateway host and service I found at SMGW (Parameters). The second one is a Logical with name RFCDE1and reference entry RFCDE1COMPANY2.
At my RFC Sender Adapter I configured the same gateway info and the same program id. After that I tested both destinations and it worked. I created the following report to call the bapi on that destinations::
REPORT ZREP_BAPI_COMPANY_GETLIST.
DATA: company_list TYPE STANDARD TABLE OF BAPI0014_1.
CALL FUNCTION 'BAPI_COMPANY_GETLIST'
IN BACKGROUND TASK
DESTINATION 'RFCDE1'
TABLES
COMPANY_LIST = company_list.
COMMIT WORK.
At SXMB_MONI the request message was processed and the output file generated, but it has only the root tag. At moni the inbound message has no data (company data).
I tested the BAPI_COMPANY_GETLIST at SE37 and there are 149 entries. When I executed this same BAPI with RFC target sys configured to my destination, it didn´t show any data and has an exception called SYSTEM_FAILURE. I think probably the error is on RFC destinations but I can´t figure it out what is wrong.
Best Regards,
GabrielaHi experts,
Thank you all for your quick response.
At the TCP/IP Destination there is a button "Unicode Test", according to this test my target system is unicode (character size 2). I changed the option at MDPM&Unicode on that TCP/IP Destination like Madhusudana described. I also selected the checkbutton "Unicode" on sender RFC communication channel.
About the sync/async, I will not use sync async bridge because this scenario can be async. One think that I realized is that when I call my report, I am implicitly calling PI asynchronously and when I call the BAPI directly by the test tool, I am implicitly calling PI synchronously. That is why most part of my tests did not work before.
Now I can see on SXMB_MONI that the scenario worked and the file was generated. But the data are still not being showed on inbound payload. I think something is wrong with my destinations but I can´t figure it out what is.
Ps.: I would prefer to use XI proxies, but this scenario will be configured (not now) on a XI 3.0 with ERP 4.6 C. Now I´m just learning how to handle with RFC Adapter.
Any ideia?
(Points granted)
Thank you and best regards,
Gabriela -
Hi,
Can somebody help me to view this thread. I am learning XI using RFC to File and I have got some difficulties in undestanding the Adapter Configuration.
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step from Michal.
When I select this thread, I get blank page.
ThanksHello MK and Shabarish,
I need a little more help from you.
Here is XI Scenario.
Want to send Material info using RFM from system A to System B via XI.
Process: In System A, I create an RFM and send the data via dest paramter.
It looks like this.
Call Function
dest 'SYSTEMA_SENDER'
1. I created T - RFC Destination in systemA.
RFC Name SYSTEMA_SENDER
gateway host gbdsc1 ( using smgw)
serveric sapgw11
Program id SystemA_Sender
Registered server program, unicode.
2. In XI box, in Integration configuration, Created RFC sender channel with the following paramter
Adapter Type RFC - Sender
RFC Server Parameter -
Applcation server(Gateway) gbdsc1 ( As in RFC dest System A )
App service(gateway) sapgw11
Program ID SystemA_Sender
RFC Metadata repository
Application Servr ( What do I enter here is it System A)
System Number
Logon on User
Logon pw
Client
Language
Finally,
In system A when I do connection test I get the following errors
Error: Program SystemA_Sender not registered
Location SAP-Gateway on gbdsc1/sapgw11
Detail:TP SystemA_Sender not registered
and other errors
Can you identify any correction required for the above RFC destination and RFC configuration?
Do I need to register the program and if so how?
Your help is deeply appreciated.
Regards -
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
Maybe you are looking for
-
Ipod nano audiobook download from CD
I have a book on CD that I want to listen to on my ipod nano. I downloaded the cd (7 in all) in my library. Then transfered to my nano. The chapters downloaded into "songs" rather than audiobooks and the chapters where all out of order. Am I missing
-
Hi guys, I understand that release transfer is used to move objects from one SWC version to another . I am having a new SWCV SRM server 7.0 ( PI content ) and a older swcv POscenarios ( having custom mappings using objects in SRM server 3.0 ) In my
-
Hi i am new to XI.how software component,technical system,Business System are related.is Business System is nothing but physically existed system in System landscape?how these are inter related.please suggest some answers Prasad
-
I am trying to get this to work so I can try http://redcareditor.com/ but I am having problems: ==> Making package: ruby-gtkmozembed 0.18.1-1 x86_64 (Wed May 6 17:28:00 EDT 2009) ==> Checking Runtime Dependencies... ==> Checking Buildtime Dependencie
-
"Un"configure Business Catalyst from contact form???
Help! I hope there is a way to have a contact form in Muse without it configured to Business Catalyst? Let me know your thoughts. Thanks in advance!