RFC Adapter RFC to File

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

Hello 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

Similar Messages

Error in pushing a request to R3 System using RFC Adapter

I am trying to send a request to R3 system using an RFC Adapter as my end point and pointing to
the Application server of the R3 box.
In the Transaction SM58 I see and error saying "Exception in handleRequest of server Xmb2RfcService: java.lang.Exception:"
Here are the corresponding details:
Caller: CENTRALADMIN
Function Module: SRFC_ADAPTER_SERVICE
Target System: AI_RFCADAPTER_JCOSERVER
Host: .... (The XI Server)
Program: SAPMSSY1
Clnt: 100
As per the SRFC_ADAPTER_SERVICE function module, the purpose stated so...
"This function is the glue between the JCo RFC Inbound Adapter and the XMS Pipeline."
By the by the RFC adapter is started and I can see no activity in the log after startup.
I would really appreciate for any idea/leads in solving this. Thanks.

Here are the details
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Config File for RFC Adapter%%%%%%%%%%%%%%%%%%%%
RFC ADAPTER CLASSNAME FOR ADAPTER ENGINE
classname=com.sap.aii.rfcadapter.core.RfcAdapterModule
RFC ADAPTER CONFIGURATION PROPERTIES
Tue Jan 21 13:27:43 CET 2003
1. GENERAL SECTION
1.1 trace settings
RfcAdapter.trace=2
-> adapter trace level 0 = none
 1 = error
 2 = standard
 3 = request
 4 = payload
 5 = binary payload outbound
#RfcAdapter.traceStack=0
#RfcAdapter.listenException=0
#RfcAdapter.listenState=0
-> additional trace switches (in general not needed)
RfcAdapter.traceFile=./LogFiles/Adapter_rfc.log
-> name of trace file (traces to stdout if not specified)
 NOTE: in a productive environment, the trace file should be written to the
 log-file directory of the Adapter Engine
1.2 connectivity settings
RfcAdapter.registerInbound=sourceBackendXD1
-> space-delimited list of logical names for inbound R/3 systems subsections.
 The adapter will register with all R/3 systems defined in this list and
 those systems can send RFC requests into the XI via an RFC destination
 that has to be setup in SM59 to point to the RFC Adapter
RfcAdapter.accessInbound=toXmb
-> logical name for inbound access to XMB subsection
RfcAdapter.registerOutbound=fromXmb
-> logical name for outbound access from XMB subsection
RfcAdapter.accessOutbound=targetBackend
-> space-delimited list of logical names for pre-allocated outbound R/3 systems subsections.
 This is an option to speed up connection setup during request processing. The RFC Adapter
 preallocates sessions to all listed R/3 systems.
RfcAdapter.clientCloseConn=1
-> close calling connections after call (1) or just reset session (0)
 NOTE: the reset mechanism is slightly faster for request processing. However, it does
 not re-connect after a target system shutdown and hence requires a restart of the
 RFC Adapter in such a situation.
#RfcAdapter.maxDynPools=128
-> maximum number of dynamically allocated client pools to access outbound R/3 systems
#RfcAdapter.minDynPoolSize=4
-> initial number of clients in dynamically allocated client pools
#RfcAdapter.incDynPoolSize=4
-> increment number of clients in dynamically allocated client pools
#RfcAdapter.maxDynPoolSize=64
-> maximum number of clients in dynamically allocated client pools
2. SUBSECTION FOR REGISTRATION TO CLIENT APPLICATION SYSTEMS
(one subsection per incoming R/3 system; requires callback service user for repository access)
RfcAdapter.sourceBackendXD1.host=db03
RfcAdapter.sourceBackendXD1.sysnr=00
RfcAdapter.sourceBackendXD1.progid=Rfc2XmbService
-> recommended is: RfcAdapter.sourceBackend.progid=Rfc2XmbService
RfcAdapter.sourceBackendXD1.poolsize=5
RfcAdapter.sourceBackendXD1.unicode=1
-> source system is Unicode installation (1) or not (0)
RfcAdapter.sourceBackendXD1.client=500
RfcAdapter.sourceBackendXD1.user=XIAPPLUSER
RfcAdapter.sourceBackendXD1.passwd=********
RfcAdapter.sourceBackendXD1.lang=EN
RfcAdapter.sourceBackendXD1.trace=2
-> enable RFC trace for this connection (1) or not (0)
#RfcAdapter.sourceBackendXD1.sncName=<SNC_name_of_adapter>
-> e.g. RfcAdapter.sourceBackendXD1.sncName=p:CN=USERNAME, O=ORGNAME, C=DE
#RfcAdapter.sourceBackendXD1.sncLib=<SNC_library_path>
-> e.g. on Win2K: RfcAdapter.sourceBackendXD1.sncLib=C:
Program Files
SECUDE
SECUDE for R3
secude.dll
#RfcAdapter.sourceBackendXD1.sncQop=<SNC_quality_of_protection>
-> 1,2,3,8,9 e.g. RfcAdapter.sourceBackendXD1.sncQop=1
#RfcAdapter.sourceBackendXD1.sncAcl=<SNC_access_control_list>
-> logical names for allowed callers e.g. RfcAdapter.sourceBackend.sncAcl=peerB6A peerB6Q
#RfcAdapter.sourceBackendXD1.sncAcl.peerB6A=p:CN=B6A, O=SAP-AG, C=DE
#RfcAdapter.sourceBackendXD1.sncAcl.peerB6Q=p:CN=B6Q, O=SAP-AG, C=DE
-> details for peer ACL lists
3. SUBSECTION FOR ACCESS TO XMB INBOUND RFC SERVICE
(only one entry possible)
RfcAdapter.toXmb.host=web03
RfcAdapter.toXmb.sysnr=00
RfcAdapter.toXmb.poolsize=5
RfcAdapter.toXmb.client=100
RfcAdapter.toXmb.user=XIAPPLUSER
RfcAdapter.toXmb.passwd=******
RfcAdapter.toXmb.lang=EN
RfcAdapter.toXmb.trace=2
4. SUBSECTION FOR REGISTRATION OF XMB OUTBOUND RFC SERVICE
(only one entry possible)
RfcAdapter.fromXmb.host=web03
RfcAdapter.fromXmb.sysnr=00
RfcAdapter.fromXmb.progid=Xmb2RfcService
this value must be in sync with Program Id setting for AI_RFCADAPTER_JCOSERVER in SM59
RfcAdapter.fromXmb.poolsize=5
RfcAdapter.fromXmb.unicode=1
-> source system is Unicode installation (1) or not (0)
RfcAdapter.fromXmb.trace=2
5. SUBSECTION FOR ACCESS TO SERVER APPLICATION SYSTEMS
(one subsection per outgoing R/3 system; pre-allocated connection pools via service user)
RfcAdapter.targetBackend.host=db03
RfcAdapter.targetBackend.sysnr=00
RfcAdapter.targetBackend.poolsize=5
RfcAdapter.targetBackend.client=500
RfcAdapter.targetBackend.user=XIAPPLUSER
RfcAdapter.targetBackend.passwd=*******
RfcAdapter.targetBackend.lang=EN
RfcAdapter.targetBackend.trace=2
END OF RFC ADAPTER CONFIGURATION PROPERTIES
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Log data for the adapter%%%%%%%%%%%%%%%%%%%%%%%%%%
Fri Sep 24 09:50:09 EDT 2004 *****
09:50:09 (6011): RFC adapter initialized
09:50:09 (6031): RFC adapter started
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%SM59 entries on the XI box%%%%%%%%%%%%%%%%%%%%%%%%%%
Name: AI_RFCADAPTER_JCOSERVER
Program ID: Xmb2RfcService
Action Type: Registered Server Program
Gateway: web03 (Local XI box)
Gateway Service: sapgw00 (00 is the system number)
Name: XI_SERVER
Program ID: Rfc2XmbService
Action Type: Registered Server Program
Gateway: db03 (R3 box)
Gateway Service: sapgw00 (00 is the system number for R3)
Both the entries are tested fine.

FILE-RFC ADAPTER problem

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 Sri

sxmb_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" ?>
- 
- <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

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

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 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. :
call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:
The File is also getting written to the destination properly. But in XI also i get the following error.
 <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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>
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,
Umesh

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

File to JDBC Using RFC Adapter.

Hi All,
I've been trying to find out a scenario which is like a File-to-Database where RFC is the sender and JDBC is at Receiver end.
Kindly guide me in:
1) What are the steps I need to do when I use a RFC Adapter to pick a file from FTP?
2) Are the steps same for the JDBC Adapter as we do normally in a JDBC Receiver Adapter?
3) Is there any other configuration required for this type of scenario?
4) If I import the RFC only I wanted to know how would the file be picked from FTP Server? Is it likewhile create a RFC we import the File from FTP server.
My Plan of Action to do the scenario is:
1) Import the RFC from R/3.
2) Create the data types for target.
3) Map them both.
4) Use JDBC Adapter on the Receiver end.
These are the steps which I think should be done, if there are any other steps which I need to do, please do tell me.
Please do let me know the steps if all the are wrong as I'm doing this type of scenario for the 1st time.
Regards,
Sreedhar.

Hi,
Though i am not very sure about your interface requirement/design but would suggest you the following links :
Sender RFC :
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
Reciever JDBC:
JDBC Stored Procedures:
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
JDBC Receiver Adapter -- Synchronous Select u2013 Step by Step
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response - XI: How-to
on JDBC receiver response

Whera can I find RFC adapter file configuration?

I search for Program ID in RFC Adapter configuration but I don't find the file properties.
Where is?
thanks,
mik

Michelle -
What verison of XI are you using? In 2.0 the configuration file ("rfc_adapter.properties") is in the tech_adapter/configuration directory on the IS; in 3.0, the program ID (for client systems) is part of the communication channel configuration in the Integration Directory. HTH; if not, please reply to this post with a more detailed question.
Paul

JDBC to File and RFC adapter

Hi All,
In my scenario, i am sending file from a database system to SAP system. Here I am using JDBC/ webserveices adapter at outbound side to query the database and FILE and RFC at inbound side to send file and workflow notification.
my requirement is to send file as batch to SAP system(after business hours), send workflow notiication to the responsible person, and when the file is stored on application server then only i should send the notification to the person.
I know this can be acheived by BPM by using wait step but I am not sure how to do it only for RFC adapter to kick the notification once the file has stored and confirmed.
Can anyone help me in this issue.
Reg
Sre.

>
sre wrote:
> Hi All,
>
> In my scenario, i am sending file from a database system to SAP system. Here I am using JDBC/ webserveices adapter at outbound side to query the database and FILE and RFC at inbound side to send file and workflow notification.
> my requirement is to send file as batch to SAP system(after business hours), send workflow notiication to the responsible person, and when the file is stored on application server then only i should send the notification to the person.
>
> I know this can be acheived by BPM by using wait step but I am not sure how to do it only for RFC adapter to kick the notification once the file has stored and confirmed.
>
> Can anyone help me in this issue.
>
> Reg
> Sre.
There are two options,
1. With BPM you can have the send step for file request an acknowledgment and then have the send step for the RFC call after the previous file send step.
2. Without BPM, use the same Business system (single receiver det.) and have multiple interface determination (file&RFC). Use the option maintain order at runtime and have the file interface above the RFC. This will act like an EOIO.

File Downloads with Adaptive RFC model

Hi,
Just curious to know as to how we can download files available as bytes from an RFC in a webdynpro Adaptive RFC model application using the FileDownLoadUI element.
Thanks,
Karambir Singh

Hi,
take a look at these links about FileDownloadUIElement ,
FileDownload UI element
How to use FileDownload UI Element?
FileDownload UI Element
hope it helps
regards

RFC -File Sync Async bridge RFC Adapter Exception

Hi
I am using sync async bridge to send a response back to rfc.
Although there is no error in sxmb_moni as well as the auditlog shows that the response was sent successfully to rfc.. still the RFC adapter gives the following error with no response sent to RFC..
Error in processing caused by: com.sap.aii.af.rfc.RfcAdapterException: failed to identify XML document:java.lang.Exception: javax.xml.parsers.FactoryConfigurationError: Provider com.sap.engine.lib.jaxp.SAXParserFactoryImpl not found
please help

Solved the problem..
The problem could be due to the following..
1. the response structure was just a single character..while i was sending a whole string..
2. I restarted the server...probably the problem
javax.xml.parsers.FactoryConfigurationError: Provider com.sap.engine.lib.jaxp.SAXParserFactoryImpl not found
system property must have set mismatch for the SAXFactoryImpl.... by deploying modules before in which i was using SAX parser.. may be the i set the system property earlier to other provider dont remember...
Hope this information will be useful to someone in future using Sync/Async bridge

Error while importing a Adaptive RFC Model

Experts,
I am trying to import an Adaptive RFC Model. Before importing I need to speciy the connection parameters in the import wizard. I am using the single server method to connect and have specified all the parameters correctly. I have not specified a SAP router as I am using a test system. when I click next on the Model import wizard I get an error.
The trace shows-
[code]ConnectionFailed Exception : com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
Connect_PM GWHOST=test833, GWSERV=sapgw00, ASHOST=test833, SYSNR=00
LOCATION CPIC (TCP/IP) on local host
ERROR partner not reached (host 10.3.82.177, service 3300)
TIME Fri Jun 29 08:54:18 2007
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8715
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUN
 at com.sap.ide.jcb.core.service.connection.internal.ConnectionManager.connect(ConnectionManager.java:220)
 at com.sap.ide.jcb.core.service.connection.internal.ConnectionManager.connectToSingleServer(ConnectionManager.java:206)
 at com.sap.ide.jcb.core.wizardpages.SAPLogonPage.internalConnectToServer(SAPLogonPage.java:1769)
 at com.sap.ide.jcb.core.wizardpages.SAPLogonPage.access$2300(SAPLogonPage.java:46)
 at com.sap.ide.jcb.core.wizardpages.SAPLogonPage$9.run(SAPLogonPage.java:1730)
 at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
 at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:98)
 at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:1999)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1733)
 at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:136)
 at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:261)
 at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
 at com.sap.ide.jcb.core.wizardpages.SAPLogonPage.connectToServer(SAPLogonPage.java:1699)
 at com.sap.ide.jcb.core.wizardpages.SAPLogonPage.performFinish(SAPLogonPage.java:1805)
 at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelWizard.initializeReimporter(ModelWizard.java:1410)
 at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelWizard.performPostSapLogonPageForReimport(ModelWizard.java:1433)
 at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelDialog.nextPressed(ModelDialog.java:85)
 at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316)
 at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
 at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
 at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
 at org.eclipse.jface.window.Window.open(Window.java:563)
 at com.sap.ide.webdynpro.modeleditor.ModelEditorCallback.reimportModel(ModelEditorCallback.java:218)
 at com.sap.ide.webdynpro.service.modeleditor.ModelService.reImportModel(ModelService.java:207)
 at com.sap.ide.webdynpro.service.modeleditor.ServiceWithUI.reImportModel(ServiceWithUI.java:120)
 at com.sap.ide.webdynpro.tsmodel.application.actions.ReimportModelAction.run(ReimportModelAction.java:11)
 at com.sap.ide.webdynpro.projectbrowser.actions.PBReimportModelAction.run(PBReimportModelAction.java:77)
 at com.sap.ide.webdynpro.projectbrowser.actions.PBDevelopmentObjectAction.runInternal(PBDevelopmentObjectAction.java:80)
 at com.sap.ide.webdynpro.projectbrowser.actions.PBDevelopmentObjectAction.run(PBDevelopmentObjectAction.java:61)
 at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
 at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
 at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
 at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
 at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
 at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
 at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
 at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
 at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
 at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
 at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
 at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
 at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
 at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
 at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
 at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
 at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
Connect_PM GWHOST=test833, GWSERV=sapgw00, ASHOST=test833, SYSNR=00
LOCATION CPIC (TCP/IP) on local host
ERROR partner not reached (host 10.3.82.177, service 3300)
TIME Fri Jun 29 08:54:18 2007
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8715
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUN
 at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeConnect(Native Method)
 at com.sap.mw.jco.rfc.MiddlewareRFC$Client.connect(MiddlewareRFC.java:1125)
 at com.sap.mw.jco.JCO$Client.connect(JCO.java:3138)
 at com.sap.ide.jcb.core.service.connection.internal.ConnectionManager.connect(ConnectionManager.java:216)[/code]
Can someone tell me problem..
Thanks in advance,
Vineeth

In service file if entry is not there... give the enty like
sapgw<Inst.No> 33<Inst.No>/tcp
sapgw<Inst.No>s 48<Inst.No>/tcp
where <Inst.No> = System Number of your R/3 system(00 or 01...)
In host file....
ip of the server name of the server....

RFC Adapter Problem: Necessary Roles?

Hi XI Gurus,
Our team is working with a File-to-RFC scenario. We are using a custom RFC, which uses BAPI_GOODSMVT_CREATE within it, to post data for Goods issue, Goods receipt and Transfer Posting. We are using the credemtials of a user, sapxiuser, within the RFC adapter. Can anyone please tell me what are the roles that are to be maintained for this particular user at the R/3 end?
Points will be rewarded!
Thanking in anticipation,
Amitabha

Hi,
Remember to add explicit commit in the communication channel:
"
Commit Control for Individual BAPI Calls
If you want to use this communication channel to call BAPIs as remote-enabled function modules that change data in the database, set the indicator.
If executed successfully, the transaction is written to the database by calling the function module BAPI_TRANSACTION_COMMIT explicitly. If an error occurs, the transaction is rolled back by BAPI_TRANSACTION_ROLLBACK.
The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values , S, I, and W are displayed. All other values are regarded as errors.
To change this setting, set the indicator BAPI Advanced Mode.
In the Successful RETURN-TYPE Values table, enter the values that should lead to a successful execution.
"
Regards,
Wojciech

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

Hi,
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 Adapter RFC to File

Similar Messages

Maybe you are looking for