RFC Adapter Settings.

Friends ,
          I am working on a RFC to XI to Mail senerio. 2 diff adapters are required for this, as we know. From r3 perspective, I have a se38 program to run the RFC.
see the code below!
report zrfc_adapter.
data: it_final1 type standard table of zrfc_str.
*Cns :
call function 'ZRFC_XI'
EXPORTING
   bill_doc       = 'ABCD'
tables
   it_final       = it_final1.
Clear it_final1.
Refresh : it_final1.
The FM has been made RFC by selecting the Remote Function Call in
FUNCTION ZRFC_XI.
""Local Interface:
*" TABLES
*"      IT_FINAL STRUCTURE ZRFC_STR OPTIONAL
      it_final-NAME = 'Arnab Mondal'.
      it_final-TELEPHONE = '12345'.
      it_final-ADDRESS = 'abcdxyz'.
      append it_final.
ENDFUNCTION.
Now there is a setting needed in sm59. I hav read several blogs and wikis, and every where they are asking to make a TCP/IP connection where I hav to make a program ID . The program ID name can be 'anything'
Now friends I have done this, and select the activation type as Registered Server Type.
Then as per the snote : 730870 ,page 13, " To check which Program IDs are registered at the SAP Gateway the
gateway-monitor can be used via transaction SMGW. Select Goto ->
Logged on Clients. Registered RFC-Servers have a System-Type of
'REGISTER_TP'. The Program ID of the registered RFC-Servrer can be
found in column 'TP name'. Unfortunately the list within SMGW only
shows the truncated version of the Program ID (column 'TP name'). To
get the full name, the details of an entry have to be selected. As an
alternative the report RSGETALL_REG_SERVERS can be executed in
transaction SE38. The output of this report will show the full names
of the Program ID in column 'Registered PROGID'. This functionality is
also available in the function module GWY_READ_CONNECTED_SYSTEMS which
can be executed in transaction SE37.
So as per instruction when I tried to execute the program RSGETALL_REG_SERVERS, I couldnt find it in se38.
   Now the biggest query is sm59 is not taking any arbitary PROGRAM ID name!
I tried to copy a standard tcp/ip connection: GFW_ITS_RFC_DES and the program id in this is IGS.DTR, which is working perfect. I can copy and use this,, but this is not the solution. Pls some1 help me, where am I going wrong???
Thanks and Regards,
Arnab
PLs Help !!!
Arnab
Edited by: Arnab Mondal on Sep 10, 2008 7:39 AM

Hi,
You can Follow this Procedure to get Success in Test Connection
1) Create RFC Sender Channel and mention the Program ID(Any thing that u Want)
Activate all the Objects here.
Now goto SM59 in R/3 and create TCP/IP connection and mention the Same Program ID name here which u entered in RFC Sender Channel creation.
Save and test Connection. and there by check in SMGW for your Registered Program ID also
Regards
Seshagiri

Similar Messages

RFC Adapter Settings - stage 2 problems

Friends ,
I am working on a RFC to XI to Mail senerio. 2 diff adapters are required for this, as we know. From r3 perspective, I have a se38 program to run the RFC.
see the code below!
report zrfc_adapter.
data: it_final1 type standard table of zrfc_str.
*Cns :
call function 'ZRFC_XI'
in background task destination
'R32XIRFC'
EXPORTING
bill_doc = 'ABCD'
tables
it_final = it_final1.
commit work.
clear it_final1.
refresh : it_final1.
The FM has been made RFC by selecting the Remote Function Call in
FUNCTION ZRFC_XI.
""Local Interface:
*" TABLES
*" IT_FINAL STRUCTURE ZRFC_STR OPTIONAL
it_final-NAME = 'Arnab Mondal'.
it_final-TELEPHONE = '12345'.
it_final-ADDRESS = 'abcdxyz'.
append it_final.
ENDFUNCTION.
I am getting black flag sign in sxmb_moni..,, a file is being created in the destination folder...as per file adapter settings, but the file is empty, the reason being, the sxmb_moni is sending no data in.....I donno the reason, why is not sending any load!!both communication channels are green.
I dont believe that because i have made 2 commubication channels inside 1 business system and then the ID, RD, SA and RA , so this is not sending the data..
I hav made 2 messege interfaces, the RFC as outbound and async, and the file as inbound and async .......is that ok???
Pls comment !!
Thanks and Regards,
Arnab
PLs Help !!!
Arnab

Nallam,
the function module is working fine in R3.It is not giving any syntatical error or short dump. But , how do i test it in xi?? what load is it sending.??? ..because , i believe there is only 1 way to check load in XI and that is through sxmb_moni...do u know any other way by which i can confirm, what load is coming into XI???? through this FM!!
Pls tell.!!
Thanks
Arnab .

RFC Adapter Settings - stage 3 problems

Hi Experts,
 Mine is a RFC to FILE scenerio.I am facing a strange problem. I am sending some data to the RFC through a SE38 program, but only a part of the data is reaching the SXMB_MONI!
See the report program and the Remote function Module below. also the details of the structure is given below:
REPORT ZRFC_ADAPTER.
Data: it_final1 type standard table of zrfc_str with header line .
 it_final1-NAME = 'ArnaB'.
 it_final1-ADDRESS = 'address'.
 it_final1-EMAIL = 'arnab.rudra1gmail'.
 it_final1-ID = 'ID'.
 append it_final1.
CALL FUNCTION 'ZRFC_XI'
IN BACKGROUND TASK DESTINATION
'R32XIRFC'
EXPORTING
 username = sy-uname
tables
 it_final = it_final1 .
break-point.
COMMIT WORK.
Clear it_final1.
I have seen in debugging mode, after removing the "
IN BACKGROUND TASK DESTINATION
'R32XIRFC'", that the internal table " it_final1 " is working fine......
The RFC structure
IT_FINAL LIKE ZRFC_STR -- in tables parameter. and the structure of ZRFC_STR is as follows!
NAME ZNAME CHAR 14
ADDRESS ZADDRESS CHAR 40
TELEPHONE ZTEL CHAR 20
EMAIL ZEMAIL CHAR 40
ID ZID CHAR 10
But when checking the SXMB_MONI load , data is incomplete and cut.......Now many of you will suggest re-importing teh RFC in Integratio Repository, and reactivating the communication channel, but i hav done that several times,,,,still the data coming in is incomplete and shreded...i donno why...take a look at teh sxmb_moni output!!
- <rfc:ZRFC_XI xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<USERNAME>RETAILDEV</USERNAME>
- <IT_FINAL>
- <item>
<NAME />
<TELEPHONE>rudra1</TELEPHONE>
<ADDRESS />
<EMAIL />
<ID />
</item>
</IT_FINAL>
</rfc:ZRFC_XI>
I know, that there is nothin getting stuck in the queue, and had there been anything wrong in the code, nothin would hav worked.....can u guys tell me where am i gettin stuck..
Regards,
Arnab

Hi Bhavesh,
 I did exactly as instructed by u some time back, I believe I hav something or other there wrong in my SE38 report, ......I cant make that out, but dont you think, this is funny, only a part of the data is coming in, and not the full...if there was something wrong, entire load would have vanished!!!..and yes I hav used the COMMIT statement....take a look at the SE38 Code,
REPORT ZRFC_ADAPTER.
Data: it_final1 type standard table of zrfc_str with header line .
 it_final1-NAME = 'ArnaB'.
 it_final1-ADDRESS = 'address'.
 it_final1-EMAIL = 'arnab.rudra1gmail'.
 it_final1-ID = 'ID'.
 append it_final1.
CALL FUNCTION 'ZRFC_XI'
IN BACKGROUND TASK DESTINATION
'R32XIRFC'
EXPORTING
 username = sy-uname
tables
 it_final = it_final1 .
break-point.
COMMIT WORK.
Clear it_final1.
Is the loaction of commit work ok.....or do you want me to put it in the Remote Function Module??
Do you think I should put the question in ABAP forum, so that some Remote function Module expert can suggest something....
Pls suggest....
Arnab

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.

Hi in my interface RFC adapter and XI adapter

Hi all,
in my interafce they are using XI adapter for data transfering for a BAPI in SCM sever , but i dont why ther using this adapter instead of RFC adapter , any one can tell me difference for this one
thanking you
sridhar

Hi,
You can configure the XI adapter to exchange messages with an Integration Engine. Both XI 3.0 and XI 2.0 message protocols are supported. You also use the XI adapter to exchange messages between SAP Exchange Infrastructure and the Partner Connectivity Kit (PCK).
You can use security settings to sign messages and check the signature. You can encrypt and decrypt message payloads.
The RFC adapter enables you to use the functions of the Integration Engine or the PCK in existing SAP landscapes. It is used by SAP systems to connect to the Integration Engine or the PCK by using the RFC interface. It supports SAP systems as of version 3.1x
See the below links to ref
http://help.sap.com/saphelp_nw04/helpdata/en/e1/091640a991c742e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
Regards
Chilla..

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

Receiver RFC adapter issue! Please help!

Hi Experts,
I have 4 XI interfaces. All of these are Webservice to RFC scenarios. Moreover all of them are synchronous.
Request message: Webservice (SOAP Adapter) ---> XI -
> RFc Adapter ---> ECC Function modules
Response message: Webservice (SOAP Adapter) <- XI < RFc Adapter <- ECC Function modules
As you can see above, external system calls XI web service via SOAP Adapter. The input data is then sent from SOAP Adapter to RFC adapter to call RFC function module in the receiving side. The receiving system is SAP ECC system.
The receiver ECC system has two instances. For example SP0 ad SP1.
In the receiver determination step we have maintained a rule such that if the Plant value in the input message is XYZ then send data to SP0. But if the plant value in ABC then send data to SP1.
This Conditional rule is working fine.
However we are getting couple of issues with only one instance of ECC (SP0).
1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-001cc495e48a(INBOUND) expired
2. NO_MAPPINGPROGRAM_FOUND. Mapping program is not available in runtime cache: Object ID C2B41FFDFD4635BAB1E41AE53C0D10CE Software Component 5394F420463611DAC1CFFBBC0A01BC16
3. com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available
The above listed errors are generated occasionally. Sometimes no errors are generated even when the same input data is sent again and message is successfully processed.
I have verified the input data and everything is OK with that.
Mapping object is available in XI and cache was also refreshed. I additionally reactivated the objects in XI as well.
So what could be the real root cause of this? Please help!
Thanks
Gopal

1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-
001cc495e48a(INBOUND) expired
Check the Timeout parameter of your adapter.....for requests which expire with this error confirm from the SAP end that the message processing is done well within the Timeout period of the adapter.
Refer this note for more info on the above occuring error and the possible way to avoid it: https://service.sap.com/sap/support/notes/791379
Update:
Even problem 3 seems to be occuring due to insufficient Timeout specified for the adapter.....if possible try increasing the Timeout in VA
Regards,
Abhishek.
Edited by: abhishek salvi on Oct 6, 2009 1:42 PM

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

Error while doing commint from RFC Adapter

Hi,
We have a SOAP-PI-RFC synchronous scenario. Through this Soap request comes to PI and passed on to BAPI via RFC adapter. This BAPI saves the transaction & return the document number. We are using " PI PI parameter u201CCommit Handling for single BAPI' in RFC receiver Channel.
While this setup works for 1 posting, when we do the mass load ( Say 20 Documents) half of the documents are not able to Save. Although BAPI, returns the document number but on checking the document does not exists in SAP. To do further test, we created a program in ECC and try calling BAPI in loop and calling BAPI Commit.
This way program works fine and there is no error
So in nutshell, when we PI do the commit, half of the documents are not saving where as when the ABAP program commits no error. Is there any special way that PI calls this commit work.
PS: We created a wrapper BAPI which calls the orgirnal BAPI and Commit BAPI & called this from PI but still the same problem is coming.
Appreciate help on this.
Regards,
Harish

Are there any error messages in the RFC Reciever channel in Runtime Workbench?
RWB -> Component monitoing -> Adapter Engine -> Comm Channel -> filter for type RFC
Please try to give some more details on why the system says the messages are failing.

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

Restrict messages in RFC adapter or in source/sending (SAP R/3) system

Hi All,
I have SAP R/3 to web service scenario via XI (RFC to SOAP). In that scenario RFC caries the attachments, some time the attachments size is more than 5mb. Due to that java stack of XI becomes unresponsive. Due to that SMQ2 gets filled up with the entries and other scenarios are also severely effecting.
Is there any way to restrict the message, if itu2019s size is more than 5mb in RFC adapter of XI or can we stop the processing/sending of such a messages in source system itself (SAP R/3).
I welcome all your suggestions.
Thanks & Regards,
Venu V

Hi Praveen,
The attachments to the tickets in source system. The RFC caries that data, once that data size is more than 5mb then it affecting the server.
I am getting following errors
u201Ccom.sap.aii.af.ra.ms.api.DeliveryException: Could not create Message from TransportMessage. Reason: com.sap.aii.af.ra.ms.api.MessagingException: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to Read timeout. The client has disconnected or a synchronization error has occurred. Read [45434] bytes. Expected [101981].u201D
u201CJCO_COMMUNICATION_FAILURE
Error opening an RFC connection
"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connectionu201D
Thanks & Regards,
Venu V

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

Dynamic user in RFC Adapter

I configure a RFC Receiver adapter to communicate with R/3. In my client application (via Webdynpro) I send the message that use this communication, but I need to call the RFC using a dynamic user/password, that is, the user credentials that is logged. Is it possible? How I do it?
thanks.

Hi Elton,
I don't think so, it is possible to have dynamic user ID and password for the RFC adapter. As of now...
Because you need to enter the user id and password while configuring adapter itself.
But if you want , you can call different RFCs based on the Condition etc.
Hope this helps,
Regards,
Moorthy

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

RFC Adapter Settings.

Similar Messages

Maybe you are looking for