Sender RFC error

Hi guys,
I'm doing an RFC to File async scenario just as mentioned in the blog
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
and i have done the configurations also from the blog
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Now when i execute my report to call the bapi with the rfc destination of my XI server, i'm getting error in sm58 of R/3 as Bean Z_BAPINAME not found. I'm not getting any messages in to XI also..
Please help me on this guys
Thanks
Varun

When i'm creating RFC destination in R/3 which gateway host and gateway service should i enter??
values from R/3 should be entered.
These you can find in transaction smgw, in menu Go To> Parameters> display
here you will get values for gateway host and gateway service of R/3
you should create RFC dest of type TCP/IP, Give a program ID .. it could be anything. This program ID you will have to provide in RFC adapter. Activate the adapter
Then Try to activate RFC dest at R/3.
For more refer
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

Similar Messages

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.

RFC error when sending logon data

Hi;
We cannot configure the STMS of our development system. When we try to
configure it, system gives an error message: Errors during distribution
of tp configuration; TMS Alert Viewers tells us
RFC_COMMUNICATION_FAILURE: RFC communications error with
system/destination TMSADM-FKT.DOMAIN_FKT RFC error when sending logon
data and READ_PROFILE_FAILED:File
erptest\sapmnt\trans\bin\TPPARAM
could not be opened for reading (No such file or directory).
Is there any advise for solution?
Best regards
Noyan
PS: Please find the profiles below:
START:
#.*       Start profile START_DVEBMGS00_erptest                                                                                *
#.*       Version                 = 000006                                                                                *
#.*       Generated by user = BASIS                                                                                *
#.*       Generated on = 30.12.2010 , 15:40:55                                                                                *
generated by R3SETUP
SAPSYSTEMNAME = FKT
INSTANCE_NAME = DVEBMGS00
SAPSYSTEM = 00
SAPGLOBALHOST = erptest
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
start database
#_DB = strdbs.cmd
#Start_Program_02 = immediate $(DIR_EXECUTABLE)\$(_DB) FKT
start message server
#_MS = msg_server.exe
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start IGS
Start_Program_05 = local $(DIR_EXECUTABLE)$(DIR_SEP)igswd$(FT_EXE) -mode=profile pf=$(DIR_PROFILE)$(DIR_SEP)FKT_DVEBMGS00_erptest
start application server
#_DW = disp+work.exe
#Start_Program_04 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS
General parameters for starting the system
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPSYSTEM = 00
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPSYSTEMNAME = FKT
#parameter created                          by: BASIS        24.12.2007 23:53:27
#INSTANCE_NAME = DVEBMGS00
#parameter created                          by: BASIS        24.12.2007 23:53:27
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPGLOBALHOST = erptest
Start database
#parameter created                          by: BASIS        24.12.2007 23:53:27
_DB = strdbs.cmd
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_01 = immediate $(DIR_EXECUTABLE)\$(_DB) $(SAPSYSTEMNAME)
Start message server
#parameter created                          by: BASIS        24.12.2007 23:53:27
MS = msgserver.exe
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_02 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start applications server
#parameter created                          by: BASIS        24.12.2007 23:53:27
_DW = disp+work.exe
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
DEFAULT:
SAPDBHOST = ERPTEST
dbms/type = mss
dbs/mss/server = ERPTEST
dbs/mss/dbname = FKT
dbs/mss/schema = fkt
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPFQDN = tr.delta.is
SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN)
SAPDBHOST = erptest
SAPTRANSHOST = erptest
DIR_TRANS =
$(SAPTRANSHOST)\sapmnt\trans
#DIR_TRANS = D:\usr\sap\trans
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
SAP Message Server for ABAP
rdisp/mshost = erptest
rdisp/sna_gateway = erptest
rdisp/sna_gw_service = sapgw00
rdisp/vbname = erptest_FKT_00
rdisp/enqname = erptest_FKT_00
rdisp/btcname = erptest_FKT_00
rdisp/msserv = sapmsFKT
rdisp/msserv_internal = 3900
rdisp/bufrefmode = sendoff,exeauto
login/system_client = 200
#GUVENLIK PARAMETRELERI
login/password_expiration_time = 90
login/min_password_lng = 6
#parameter created                          by: BASIS        25.03.2004 08:41:25
rdisp/gui_auto_logout = 10800
#parameter created                          by: BASIS        25.03.2004 08:37:47
#old_value: 3                                 changed: BASIS 25.03.2004 08:42:38
login/fails_to_user_lock = 6
#validasyon geregi, g#venligi artirma ama#i - check active but no check for SRF
#parameter created                          by: BASIS        16.06.2007 17:35:41
#old_value: 2
#changed: BASIS         14.05.2008 15:24:55
auth/rfc_authority_check = 1
#otomatik unlocki iptal eder
#parameter created                          by: BASIS        10.11.2006 17:47:15
login/failed_user_auto_unlock = 0
#AUDIT PARAMETRELER?
#old_value:                                   changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_day = 1996800000
#old_value: 1000000000                        changed: BASIS 20.04.2005 17:17:01
#old_value: 0                                 changed: BASIS 20.04.2005 17:19:12
rsau/max_diskspace/local = 2048000000
#old_value: 2000000000                        changed: BASIS 28.03.2005 23:17:11
#old_value: 2                                 changed: BASIS 29.03.2005 12:09:14
#old_value: 0                                 changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_file = 665600000
rsau/enable = 1
rsau/local/file = D:\usr\sap\FKT\DVEBMGS00\log\++++++++######..AUD
rsau/selection_slots = 12
#rec/client = ALL
DIR_AUDIT = D:\usr\sap\FKT\DVEBMGS00\log
FN_AUDIT = ++++++++######..AUD
#DIL PARAMETRELERI
#Turkish codepage settings
abap/import_char_conversion = 0
install/codepage/db/non_transp = 1610
install/codepage/db/transp = 1610
zcsa/installed_languages = DET
#zcsa/system_language = E
zcsa/system_language = T
zcsa/second_language = E
install/codepage/appl_server = 1610
#OS dependent
abap/locale_ctype = Turkish_turkey.28599
#DIR_PUT = D:\usr\sap\FKQ\upg\abap
   *** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/msserv_internal = 3900
#system/type = ABAP
INSTANCE:
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPSYSTEM = 00
INSTANCE_NAME = DVEBMGS00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
icm/server_port_0 = PROT=HTTP,PORT=80$$
SAP Message Server parameters are set in the DEFAULT.PFL
ms/server_port_0 = PROT=HTTP,PORT=81$$
#rdisp/wp_no_dia = 10
#rdisp/wp_no_btc = 3
#rdisp/wp_no_enq = 1
#rdisp/wp_no_vb = 1
#rdisp/wp_no_vb2 = 1
#disp/wp_no_spo = 1
rdisp/wp_no_dia = 12
rdisp/wp_no_vb = 3
rdisp/wp_no_vb2 = 0
rdisp/wp_no_enq = 1
rdisp/wp_no_btc = 3
rdisp/wp_no_spo = 1
#PERFORMANS PARAMETRELERI
#parameter created                          by: SAP*         08.08.2001 10:30:18
abap/fieldexit = yes
#parameter created                          by: ALPER        13.10.2000 18:24:16
install/collate/active = 1
rdisp/max_wprun_time = 25000
MEMORY_NO_MORE_PAGING dump nedeniyle
#parameter created                          by: BASIS        27.12.2006 17:00:22
rdisp/PG_MAXFS = 262144
abap/heap_area_nondia = 2000000000
rdisp/PG_SHM = 16384
rdisp/ROLL_SHM = 32768
#'STORAGE_PARAMETERS_WRONG_SET' or 'TSV_TNEW_PAGE_ALLOC_FAILED'
#Note 552209 - Maximum memory utilization for processes on NT/Win2000
#parameter created                          by: BASIS        30.10.2007 10:57:24
#abap/heap_area_nondia = 50000
#parameter created                          by: BASIS        30.10.2007 10:58:54
#rdisp/PG_SHM = 0
#parameter created                          by: BASIS        30.10.2007 10:58:27
#rdisp/ROLL_SHM = 625
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:49:57
dbs/mss/stats_on = 1
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:49:33
dbs/oledb/stats_on = 1
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:48:23
dbs/oledb/add_procs = 8
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:47:29
rsdb/esm/max_objects = 2000
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:47:03
rsdb/otr/buffersize_kb = 4096
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:46:21
rsdb/esm/buffersize_kb = 4096
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:18:14
ztta/parameter_area = 16000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:43
enque/table_size = 10000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:20
gw/max_sys = 2000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:01
gw/max_overflow_size = 25000000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:15:19
rdisp/max_comm_entries = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:14:48
rdisp/tm_max_no = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:14:20
gw/max_conn = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:13:42
rdisp/max_arq = 2000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:12:57
ztta/roll_area = 3500000
#parameter created                          by: BASIS        18.05.2005 09:20:25
#old_value: 90                                changed: BASIS 18.05.2005 09:22:25
rdisp/max_hold_time = 300
#parameter created                          by: BASIS        20.08.2003 12:10:20
#old_value: 6144
#changed: BASIS         03.01.2008 19:42:10
rsdb/obj/buffersize = 20000
#parameter created                          by: BASIS        20.08.2003 12:09:48
#old_value: 6000
#changed: BASIS         03.01.2008 19:42:59
rsdb/obj/max_objects = 20000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:42:11
#old_value: 250000
#changed: BASIS         30.10.2007 10:56:17
#abap/buffersize = 100000
#changed: BASIS         03.01.2008 19:40:36
#abap/buffersize = 300000
#by: BASIS 12.06.2008
abap/buffersize = 400000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:41:32
#zcsa/presentation_buffer_area = 20000000
#64 bite gectikten sonra   by: BASIS 10.06.2008
zcsa/presentation_buffer_area = 30000768
note 103747
#parameter created                          by: BASIS        08.07.2003 20:40:55
rsdb/ntab/ftabsize = 30000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:40:12
rtbb/max_tables = 500
note 103747
#parameter created                          by: BASIS        08.07.2003 20:39:15
#old_value: 20000
#changed: BASIS         03.01.2008 19:41:29
#rtbb/buffer_length = 30000
#64 bite gectikten sonra by: BASIS 10.06.2008
rtbb/buffer_length = 50000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:38:26
zcsa/db_max_buftab = 10000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:37:37
#zcsa/table_buffer_area = 50000000
#64 bite gectikten sonra   by: BASIS 10.06.2008
#zcsa/table_buffer_area = 89000000
by: BASIS 12.06.08
zcsa/table_buffer_area = 99000000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:36:54
sap/bufdir_entries = 10000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:36:12
rsdb/cua/buffersize = 8000
#note 103747
#parameter created                          by: BASIS        08.07.2003 20:34:46
#old_value: 5000                              changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/sntabsize = 5500
#parameter created                          by: BASIS        08.07.2003 20:33:56
#note 103747
#old_value: 10607                             changed: BASIS 08.07.2003 20:34:58
#old_value: 10000                             changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/irbdsize = 11000
#note 103747
#parameter created                          by: BASIS        08.07.2003 20:32:18
rsdb/ntab/entrycount = 40000
#old_value: 2076                              changed: BASIS 28.06.2005 19:36:21
#old_value: 5735                              changed: BASIS 28.06.2005 19:40:01
PHYS_MEMSIZE = 4096
#64 bite gectikten sonra   by: BASIS 10.06.2008
abap/heaplimit = 40894464
abap/heap_area_total = 2000683008
ztta/roll_extension = 2000683008
em/blocksize_KB = 4096
   *** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/elem_per_queue = 2000
#auth/auth_number_in_userbuffer = 9000
#snc/enable = 0

Hi Srikishan;
You are right. The problem was releated with secstore. I found a SAP note ( Note 1532825 - Deleting SECSTORE entries during system export/system copy). I created the program which ise mentioned in the note and than run it. After that everything seems ok now.
Thanks for your help and interest
Best regards
Noyan

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

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

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

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

RFC error while publishing dialog transaction

Dear All,
I had made an internet service in a dialog pool.But while publishing it i am getting RFC errors.Can you tell me what are the prerequisites for designing an internet servise as i want my module pool page to be displayed through internet browser.
Pratighya Jain

Hi Pratighya,
you got RFC-errors during the publishing of an internet service?
I assume you are talking about the integrated ITS.
Ok, that is what will happen if you publish an internet service:
the templates are copied to the the table containing the published ones
the MIME object are activated in order to be loadable by the icman - the
Web server part of the WebAS
The template caches on each application server of the system are invalidated.
For doing the last part we need RFC connections between the application servers,
since the order to refresh the cache is send using a function module via RFC. Is
the system configuration clean? Are all of the servers reachable by RFC?
You may check the state of the template caches using the transaction SITSPMON.
hope this helps
Tobias

RFC error in idoc to file scenario in PI 7.0

Hi Experts,
I am getting a RFC error message like this below
:u201D RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_XI_SEND_MAIL in remote system (RfcClient[RFC_REJECTION_MAIL]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught.u201D
Here Z_XI_SEND_MAIL is a customised function module which is calling some classes. This function module is responsible for sending emails to a group of people. This function module is working fine in acceptance server and development server but throwing exception in production. Thus the users are unable to receive emails. There has been no code changes in the function module. Idocs are being triggrred from sap r/3 system into XI, then being processed by a BPM, finally RFC (Z_XI_SEND_MAIL ) is being called to send email messages. SXMB_MONI is showing that the email message is being send to the RFC properly but communication channel is showing the above mentioned error.
Please suggest me what might be the reason of such errors?
Regards
Anupam

Hello,
Have you tested the production data in your acceptance system or development system for the interface?
Is it working fine??
It seems that the function module is generating exception, which could be due to data.
-Rahul

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 comm channel - program ID

Hi all,
Short question:
I have RFC to FTP scenario.
Sender RFC channel needs a program ID.
I created a TCP/IP RFC Destination in source SAP system and specified in there the program ID i will use. However, when i try to test this connection, it throws folllowing error:
Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: program SAD_TO_DXI not registered
Error Details LOCATION: SAP-Gateway on host xxxxxx / sapgw05
Error Details DETAIL: TP SAD_TO_DXI not registered
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 6852
Error Details MODULE: gwr3cpic.c
Error Details LINE: 1694
Error Details RETURN CODE: 679
Error Details SUBRC: 0
Error Details RELEASE: 700
Error Details TIME: Wed Sep 26 17:21:55 2007
Error Details VERSION: 2
Could you please tell me how can i solve this?? and confirm this is the parameter i have to specify in the Sender CC??
Thanks in advance and kind regards,
David

hi David,
I guess the connection between R/3 and XI is not proper......
Connection between XI and R/3
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Also check the program ID
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
Also check discussion
Re: Why Program ID
regards
biplab
Use a Good Subject Line, One Question Per Posting - Award Points

Problem in Sender RFC adapter

Hi all,
Our scenarion is like this
RFC -> XI -> File
When we are calling the RFC ( inside a program ) from the client we are getitng a shortdump with the error ...
'JCO.Server could not find server function 'STOCK_ENQUIRY_OUT'
any idea where is the exact problem '?
regards
Goutam

Have these basic checks;
1. Import the RFC and activate the same in XI.
2. Configuring of RFC adapter - /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
3. Troubleshooting - /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

Sender RFC-Problem in SM58

Hi all,
Currently I am working on RFC synchronous call with out using BMP.
Here we have developed two asynchronous RFC call to achieve the above requirement.
Here are the details,
1. A call from FILE-XI-RFC (Receiver), for sending the selection criteria
2. Another call from (Sender) RFC-XI-FILE for sending the response back.
Here I am going to call 2 RFCs to get the response back. Here when I am working with the scenario (2) i.e., sender RFC, I have done all the design and configuration part of it.
And when am trying to test this sender rfc from a sample ABAP report (with COMMIT WORK) the RFC gets executed without any error but when I check in SM58 all the back ground tasks gets queued and are not getting processed further.
Can anyone please help me out? Is it a configuration problem in XI or in ABAP.
Please help me. Its very urgent for me.
Thanks in advance,
-kanth.

Hi,
did you try to push the entries in SM58 -> F6 ?
do you see any error ?
also check out my blog:
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
to see if your RFC to XI is correct - you can test it from sm59
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

RFC Error when using SAPRFC against a Unicode System

Hi Everybody,
I try to use the PHP SAPRFC extension against a Unicode System. When I call the client.php which comes with the source package from http://saprfc.sourceforge.net/ where I added:
 "CODEPAGE"=>"4103", // codepage Unicode
 "UNICODE"=>"1", // Unicode
to the $LOGIN array I get this error:
Warning: RFC Error Info : Group : 103 Key : RFC_ERROR_LOGON_FAILURE Message : D
in /var/www/saprfc/client.php on line 48
RFC connection failed with error:RFC Error Info : Key : C
Status : EXCEPTION SYSTEM_FAILURE RAISED Message : D Internal:
there are two trace files after the call. One called dev_rfc.trc with this content:
**** ERROR file opened at 20060605 050220 CEST, SAP-REL 640,0,119 RFC-VER 3 818129 MT-SL
T:1079532480 Error in program 'apache2': ======> D
T:1079532480 Error in program 'apache2':
<* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
and a file called rfc27443_1079532480.trc:
**** Trace file opened at 20060605 050500 CEST, SAP-REL 640,0,119 RFC-VER 3 818129 MT-SL
<<< RfcOpenEx failed
>TS> Mon Jun 5 05:05:06 2006
resize I/O buffer to 16000 bytes
>>>> [7] <unknown> : EXT <ac: 74> L sapserver.test.com >>> OPEN
UUID: ab_drvstate create uuid {44839DD5-9DCE-6B32-E200-12FDBA107532}
>>>> [7] <unknown> : EXT <ac: 75> L sapserver.test.com >>> 45573492 (45573492)
-{44839DD5-9DCE-6B32-E200-12FDBA107532}
>>> RfcOpenEx ...
Got following connect_param string:
 ASHOST=sapserver.test.com SYSNR=00 CLIENT=002 USER=developer PASSWD=*******
LANG=EN CODEPAGE=4103 UNICODE=1 TRACE=1
Send RFCHEADER: 01/LIT/IEEE/SPACE/4103
Send UNICODE-RFCHEADER: cp:4103/ce:IGNORE/te:REJECT/cs:1/rc:0x00000023
UUID: send_rfcuuid {44839DD5-9DCE-6B32-E200-12FDBA107532}
>>> Logon check: calling RFCPING
>>> RfcCall [7] ...
*> RfcCall
FUNCTION RFCPING
 handle = 7
 parameter = <NULL>
 tables = <NULL>
UUID: RfcCallNew send the uuid to the partner {44839DD5-9DCE-6B32-E200-12FDBA107532}
>>>> [7] <unknown> : EXT <ac: 76> L sapserver.test.com >>> WRITE (45573492)
-{44839DD5-9DCE-6B32-E200-12FDBA107532}
000000 | D9C6C3F0 F0F0F0F0 F0F0F0E3 01010008 |................|
000010 | 01010101 04010003 01010103 00040000 |................|
000020 | 020B0103 0106000B 04010003 01000100 |................|
000030 | 00002301 06000700 0F313237 2E302E30 |..#......127.0.0|
000040 | 2E312020 20202020 00070011 00014500 |.1 ......E.|
000050 | 11001200 04363430 20001200 13000436 |.....640 ......6|
000060 | 34302000 13000800 20736172 67652D77 |40 ..... sarge-w|
000070 | 77772020 20202020 20202020 20202020 |ww |
000080 | 20202020 20202020 20000800 0600803C | ......<|
000090 | 756E6B6E 6F776E3E 00000000 00000000 |unknown>........|
0000a0 | 00000000 00000000 00000000 00000000 |................|
0000b0 | 00000000 00000000 00000000 00000000 |................|
0000c0 | 00000000 00000000 00000000 00000000 |................|
0000d0 | 00000000 00000000 00000000 00000000 |................|
0000e0 | 00000000 00000000 00000000 00000000 |................|
0000f0 | 00000000 00000000 00000000 00000000 |................|
000100 | 00000000 00000000 00000000 00000000 |................|
000110 | 06051400 10D59D83 44CE9D32 6BE20012 |........D..2k...|
000120 | FDBA1075 32051401 30000761 70616368 |...u2...0..apach|
000130 | 65320130 01110009 44455645 4C4F5045 |e2.0....DEVELOPE|
000140 | 52011101 17000D56 F94AFD31 E72211B4 |R......V.J.1."..|
000150 | 1DCED7F3 01170114 00033030 32011401 |..........002...|
000160 | 15000145 01150501 00010105 01050200 |...E............|
000170 | 00050200 0B000336 3430000B 01020007 |.......640......|
000180 | 52464350 494E4701 02051400 10D59D83 |RFCPING.........|
000190 | 44CE9D32 6BE20012 FDBA1075 320514FF |D..2k......u2...|
0001a0 | FF0000FF FF000000 00000000 00000000 |................|
>>>> [7] <unknown> : EXT <ac: 77> L sapserver.test.com >>> FLUSH(WRITE) (45573492)
-{44839DD5-9DCE-6B32-E200-12FDBA107532}
<* RfcCall [7] : returns 0:RFC_OK
>>>> [7] <unknown> : EXT <ac: 78> L sapserver.test.com >>> FLUSH(WRITE) (45573492)
-{44839DD5-9DCE-6B32-E200-12FDBA107532}
>>>> Listen/WaitForRequest (counter = 4)
>>>> [7] <unknown> : EXT <ac: 79> L sapserver.test.com >>> LISTEN (45573492)
-{44839DD5-9DCE-6B32-E200-12FDBA107532}
000000 | 01010008 01010101 04010003 01010103 |................|
000010 | 00040000 020B0103 0106000B 04010003 |................|
000020 | 01000200 00002301 06001600 08310031 |......#......1.1|
000030 | 00300030 00001600 07001E31 0030002E |.0.0.......1.0..|
000040 | 00310032 0038002E 00330036 002E0031 |.1.2.8...3.6...1|
000050 | 00350020 00200020 00000700 11000233 |.5. . . .......3|
000060 | 00001100 12000836 00320030 00200000 |.......6.2.0. ..|
000070 | 12001300 08360032 00300020 00001300 |.....6.2.0. ....|
000080 | 08004064 00650063 00720030 0034005F |[email protected]._|
000090 | 00430052 0034005F 00300030 00200020 |.C.R.4._.0.0. . |
0000a0 | 00200020 00200020 00200020 00200020 |. . . . . . . . |
0000b0 | 00200020 00200020 00200020 00200020 |. . . . . . . . |
0000c0 | 00200000 08000601 003C756E 6B6E6F77 |. .......<unknow|
0000d0 | 6E3E0000 00000000 00000000 00000000 |n>..............|
0000e0 | 00000000 00000000 00000000 00000000 |................|
0000f0 | 00000000 00000000 00000000 00000000 |................|
000100 | 00000000 00000000 00000000 00000000 |................|
000110 | 00000000 00000000 00000000 00000000 |................|
000120 | 00000000 00000000 00000000 00000000 |................|
000130 | 00000000 00000000 00000000 00000000 |................|
000140 | 00000000 00000000 00000000 00000000 |................|
000150 | 00000000 00000000 00000000 00000000 |................|
000160 | 00000000 00000000 00000000 00000000 |................|
000170 | 00000000 00000000 00000000 00000000 |................|
000180 | 00000000 00000000 00000000 00000000 |................|
000190 | 00000000 00000000 00000000 00000000 |................|
0001a0 | 00000000 00000000 00000000 00000000 |................|
0001b0 | 00000000 00000000 00000000 00000000 |................|
0001c0 | 00000000 00000000 00000605 140010D5 |................|
0001d0 | 9D8344CE 9D326BE2 0012FDBA 10753205 |..D..2k......u2.|
0001e0 | 14050000 00050004 03002E43 0041004C |...........C.A.L|
0001f0 | 004C005F 00460055 004E0043 00540049 |.L._.F.U.N.C.T.I|
000200 | 004F004E 005F004E 004F0054 005F0046 |.O.N._.N.O.T._.F|
000210 | 004F0055 004E0044 00040304 02004046 |.O.U.N.D......@F|
000220 | 0075006E 00630074 0069006F 006E0020 |.u.n.c.t.i.o.n. |
000230 | 006D006F 00640075 006C0065 00200022 |.m.o.d.u.l.e. ."|
000240 | 00524643 50494E22 0020006E 006F0074 |.RFCPIN". .n.o.t|
000250 | 00200066 006F0075 006E0064 002E0004 |. .f.o.u.n.d....|
000260 | 02FFFF00 00FFFF00 00000000 00000000 |................|
<* RfcListen [7] : returns 0:RFC_OK
>>> RfcReceive [7] ...
Received RFCHEADER [7]: 01/LIT/IEEE/SPACE/4103
Received UNICODE-RFCHEADER [7]: cp:4103/ce:IGNORE/te:REJECT/cs:2/rc:0x00000023
UUID: ab_rfccheck_uuid compare uuid's {44839DD5-9DCE-6B32-E200-12FDBA107532}
Error in program 'apache2': ======> F
>>>> [7] <unknown> : EXT <ac: 80> L sapserver.test.com >>> CLOSE abrfcrcv_mt.c 429 (45573492)
-{44839DD5-9DCE-6B32-E200-12FDBA107532}
*> RfcReceive
 handle = 7
 parameter = <NULL>
 tables = <NULL>
 Data conversion On
Error in program 'apache2': <* RfcReceive [7] : returns 3:RFC_SYS_EXCEPTION
>>>> [7] <unknown> : EXT <ac: 81> L sapserver.test.com >>> FREE abrfcio_mt.c 3517 (45573492)
-{44839DD5-9DCE-6B32-E200-12FDBA107532}
**** Trace file opened at 20060605 050506 CEST, SAP-REL 640,0,119 RFC-VER 3 818129 MT-SL
<<< RfcOpenEx failed
Our SAP Environment is:
- SAP Web AS 6.20 Unicode Kernel Patchlevel 1602
- Windows 2003 Server
- Oracle
On the PHP Side I use:
- Debian GNU/Linux 3.1 (Sarge)
- Apache 2 2.0.54-5
- PHP4 4.3.10-16
- SAPRFC 1.4.1
- SAP RFC SDK non Unicode 6.20 and 6.40 (The problem occurs in both versions)
Had anyone had sucess using SAPRFC against a Unicode System?
Regards
Gregor

Hi Anton,
I've just tried your suggestion. I've commented out the CODEPAGE and UNICODE values in my Array and placed:
[code]saprfc_set_code_page($rfc, "4103");[/code]
after the
[code]$rfc = saprfc_open ($LOGIN);[/code]
The error message I get now is:
[code]Warning: RFC Error Info : Key : Status : EXCEPTION FU_NOT_FOUND RAISED Message :
Internal: in /var/www/saprfc/client.php on line 58
Discovering interface of function module RFC_READ_REPORT failed[/code]
In the trace File I see:
[code]>>>> [3] <unknown> : EXT <ac: 40> L sapserver.test.com >>> WRITE (80999721)
-{44839E3E-9E3B-6B30-E200-0534B0CD3057}
000000 | 05020000 0502000B 00063600 34003000 |..........6.4.0.|
000010 | 000B0102 00385200 46004300 5F004700 |.....8R.F.C._.G.|
000020 | 45005400 5F004600 55004E00 43005400 |E.T._.F.U.N.C.T.|
000030 | 49004F00 4E005F00 49004E00 54004500 |I.O.N._.I.N.T.E.|
000040 | 52004600 41004300 45005F00 50000102 |R.F.A.C.E._.P...|
000050 | 05140010 3E9E8344 3B9E306B E2000534 |....>..D;.0k...4|
000060 | B0CD3057 05140201 00104600 55004E00 |..0W......F.U.N.|
000070 | 43004E00 41004D00 45000201 0203001E |C.N.A.M.E.......|
000080 | 5246435F 52454144 5F524550 4F525420 |RFC_READ_REPORT |
000090 | 20202020 20202020 20202020 20200203 | ..|
0000a0 | 03010010 50004100 52004100 4D005300 |....P.A.R.A.M.S.|
0000b0 | 5F005000 03010330 00040000 00010330 |_.P....0.......0|
0000c0 | 03020008 000000D8 00000000 0302FFFF |................|
0000d0 | 0000FFFF 00000000 00000000 00000000 |................|
>>>> [3] <unknown> : EXT <ac: 41> L sapserver.test.com >>> FLUSH(WRITE) (80999721)
-{44839E3E-9E3B-6B30-E200-0534B0CD3057}
<* RfcCall [3] : returns 0:RFC_OK
>>> RfcReceive [3] ...
>>>> [3] <unknown> : EXT <ac: 42> L sapserver.test.com >>> FLUSH(WRITE) (80999721)
-{44839E3E-9E3B-6B30-E200-0534B0CD3057}
>>>> [3] <unknown> : EXT <ac: 43> L sapserver.test.com >>> READ (80999721)
-{44839E3E-9E3B-6B30-E200-0534B0CD3057}
000000 | 05000000 05000415 00044600 4C000415 |..........F.L...|
000010 | 04160002 45000416 04170006 30003400 |....E.......0.4.|
000020 | 36000417 04010018 46005500 5F004E00 |6.......F.U._.N.|
000030 | 4F005400 5F004600 4F005500 4E004400 |O.T._.F.O.U.N.D.|
000040 | 0401FFFF 0000FFFF 00000000 00000000 |................|
>>>> [3] <unknown> : EXT <ac: 44> L sapserver.test.com >>> FLUSH (READ) (80999721)
-{44839E3E-9E3B-6B30-E200-0534B0CD3057}[/code]
Regards
Gregor

CALL_FUNCTION_REMOTE_ERROR when trying to call Sender RFC

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

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

Correct and re-send the error messages in PI

Hi everyone,
Today when iam monitoring my PI i found error like some objects missing in the que, I toublshooted it by using inbount xml payload and found the error and cunsulted the user he asked me to correct and re-send the error messages. as iam really new to PI monitoring i really dont know how to correct and re-send the error messages in PI, can any one please help me with it.
Thanks in advance

When you send the messages from RWB-->Component Monitoring ->Integration Engine>test message, runtime parameters like Sender System, Receiver system, Adapter specific message attributes won't carry any values. If you are using any of these paramters in the mapping step,, the mapping will fail.
I think in your case, RFC look up would have been configured based on Sender Business system/Service. but when you send message from RWB, the value for this field is empty. So that is why it is failing as the message cannot find the business system and communication channel.
If you use the sender file name, server name or any other parameters in the message mapping, then message will fail in the message mapping step. That is the major set back in RWB-->Test message.
Reasons:
1)We post messages directly into pipeline step message mapping.
2)The previous pipeline steps are ignored when post messages from RWB such as Receiver determination, routing etc
3)Receiver determination step is responsible to send Sender/Receiver values into the mapping step.
Hope i have clarified your questions

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 error

Similar Messages

Maybe you are looking for