Receiver RFC Problem

Hi All,
I have a scenario File to RFC. Before it used to work fine until i received a connection error. Basis restarted the adapter using Visual Admin tool. Now the problem is nothing comes through from to the RFC adapter. I am getting no error. In the communication monitory, its showing no activity.
What could be the problem?
Tks,
D

The problem is still there if run the interface 1 more time. Can you guyz make sense of the below text. This comes from a file from the dev_jrfc_trc files on the server.
Error> occured >Thu Oct 25 10:59:37,625<
RfcException:
    message: Connect to message server host failed
Connect_PM TYPE=B MSHOST=sapxd1ci1 GROUP=PUBLIC R3NAME=XD1 MSSERV=sapmsXD1 PCS=1
ERROR       Group PUBLIC not found
TIME        Thu Oct 25 10:59:37 2007
RELEASE     640
COMPONENT   LG
VERSION     5
RC          -6
MODULE      lgxx.c
LINE        3541
DETAIL      LgIGroup
COUNTER     1
    Return code: RFC_FAILURE(1)
    error group: 102
    key: RFC_ERROR_COMMUNICATION
Error> occured >Thu Oct 25 12:13:05,579<
RfcException:
    message: Connect to message server host failed
Connect_PM TYPE=B MSHOST=sapxd1ci1 GROUP=PUBLIC R3NAME=XD1 MSSERV=sapmsXD1 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       Group PUBLIC not found
TIME        Thu Oct 25 12:13:05 2007
RELEASE     640
COMPONENT   LG
VERSION     5
RC          -6
MODULE      lgxx.c
LINE        3541
DETAIL      LgIGroup
COUNTER     3
    Return code: RFC_FAILURE(1)
    error group: 102
    key: RFC_ERROR_COMMUNICATION
Error> occured >Thu Oct 25 13:20:46,630<
RfcException:
    message: Connect to message server host failed
Connect_PM TYPE=B MSHOST=sapxd1ci1 GROUP=PUBLIC R3NAME=XD1 MSSERV=sapmsXD1 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       Group PUBLIC not found
TIME        Thu Oct 25 13:20:46 2007
RELEASE     640
COMPONENT   LG
VERSION     5
RC          -6
MODULE      lgxx.c
LINE        3541
DETAIL      LgIGroup
COUNTER     2
    Return code: RFC_FAILURE(1)
    error group: 102
    key: RFC_ERROR_COMMUNICATION

Similar Messages

RFC problem: could not get functionname from XML requst (sic)

I'm developing an interface that attempts to call a receiver RFC on an SAP 4.6c system. It's a very small simple interface, and it's all working until it tries to call the RFC. The error is
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get functionname from XML requst: com.sap.aii.af.rfc.RfcAdapterException: failed to read funtionname from XML document: missing namespace declara
I've created an RFC channel, which is green in the adapter monitoring. The RFC imports without a problem, and appears in my interface mapping. My mapping program converts to the RFC message type (as evidenced in sxmb_moni. I have a receiver agreement referencing the interface mapping, which must be working as the mapping is called.
Could anyone point me to what else I could check? I saw a post about the same error message, where the respondent found something in the logs which helped them Could you expand on what you found, and in which log please? Any pointers as to which logging options I could switch on and check would be gratefully received.
Regards
Alan Graham

Thanks for the responses.
I set up a communications channel of type RFC, which is
showing green in the adapter monitor. If I deliberately
break it, eg by changing the password, the adapter shows
as red in the monitor. I assume therefore that the
adaptor settings are correct.
The XML going to the adapter looks correct AFAIK. My problem is that I don't know enough about the requied XML to know if what I'm seeing in the logs is sufficient. In SXMB_MONI, in the 'call adapter' section of a failed message, the outbound binding includes
<SAP:ToInterfaceNamespace>urn:sap-com:document:sap:rfc:functions</SAP:ToInterfaceNamespace>/code]
Also, the interface determination SOAP header, in the MAIN section includes
[code]<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>D04</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">Z_MPU_3PSCE_FREIGHT_UPLOAD</SAP:Interface>
</SAP:Receiver>
These are the correct values for the RFC name and the namespace, AFAIK.
I'm using an interface mapping (which uses and ABAP class as the mapping program) which references the interface of the RFC. The logs tell me this works, ie, the class is called and the resulting XML appears in the payload of the response.
Alan

SOAP - XI - RFC / Problem with timeout-handle

hi gurus
B I G U R G E N T problem. how can it be:
- i've got an custom-bapi
- in receiver-rfc-adapter 'commit-controller' is on
when i force an time-out in sap ecc the soap-caller receives an system-error 'time-out...'.
but: the custom-bapi becomes an commit and in ecc the document is booked!
how can it be?
thanks
t

hi Rajesh
in sxmb_moni the message has the status 'log-version'.
soap-adapter-log:
2010-06-24 17:04:42 Erfolgreich calling the module processor for channel CC_SD01_WS_OUT
2010-06-24 17:04:42 Erfolgreich MP: Tritt in den Modulprozessor ein
2010-06-24 17:04:42 Erfolgreich MP: Lokales Modul localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean wird verarbeitet
2010-06-24 17:04:42 Erfolgreich SOAP: request message entering the adapter with user KOMM
2010-06-24 17:04:42 Erfolgreich SOAP: request message leaving the adapter (call)
2010-06-24 17:04:42 Erfolgreich Die Anwendung versucht eine XI Message synchron zu senden über SOAP_http://sap.com/xi/XI/System
2010-06-24 17:04:42 Erfolgreich Versuch die Message in die Call-Queue zu stellen
2010-06-24 17:04:42 Erfolgreich Message erfolgreich in Queue gestellt
2010-06-24 17:04:42 Erfolgreich Die Message wurde erfolgreich aus der Call-Queue abgerufen
2010-06-24 17:04:42 Erfolgreich Der Status der Message wurde auf DLNG gesetzt
2010-06-24 17:05:47 Fehler Rückgabe synchroner Fehlerbenachrichtigung an rufende Anwendung: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Timeout.
2010-06-24 17:05:47 Fehler Die Übertragung der Message über http://szhm2179:8001/sap/xi/engine?type=entry ist fehlgeschlagen, weil: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
2010-06-24 17:05:47 Fehler Der Status der Message wurde auf FAIL gesetzt
2010-06-24 17:05:47 Fehler Zurück zur Anwendung. Ausnahme: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
2010-06-24 17:05:47 Fehler SOAP: call failed: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
2010-06-24 17:05:47 Fehler SOAP: call failed: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
2010-06-24 17:05:47 Fehler MP: Ausnahme aufgetreten mit Grund com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Timeout: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
rfc-adapter-log:
2010-06-24 17:04:43 Erfolgreich Message wurde erfolgreich vom Messaging-System empfangen. Profil: XI URL: http://szhm2179.stzh.ch:50100/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2010-06-24 17:04:43 Erfolgreich Mit der Verbindung RFC_http://sap.com/xi/XI/System. Versuch die Message in die Request-Queue zu stellen
2010-06-24 17:04:43 Erfolgreich Message erfolgreich in Queue gestellt
2010-06-24 17:04:43 Erfolgreich Die Message wurde erfolgreich von der Request-Queue abgerufen
2010-06-24 17:04:43 Erfolgreich Der Status der Message wurde auf DLNG gesetzt
2010-06-24 17:04:43 Erfolgreich Liefert an Kanal: CC_SD01_RFC_IN
2010-06-24 17:04:43 Erfolgreich MP: Tritt in den Modulprozessor ein
2010-06-24 17:04:43 Erfolgreich MP: Lokales Modul localejbs/RfcAFBean wird verarbeitet
2010-06-24 17:04:43 Erfolgreich RFC-Adapter hat synchrone Message erhalten. Versucht, sRFC für /STZH/SOZ_CD_F2_BELEG_CREATE zu senden
2010-06-24 17:04:43 Erfolgreich RFC-Adapter hat synchrone Message erhalten. Versucht, sRFC für J2EE_GUEST zu senden
2010-06-24 17:05:47 Fehler SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Timeout: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
2010-06-24 17:08:43 Erfolgreich BAPI-Response war eine Struktur des Typs BAPIRET2
2010-06-24 17:08:43 Erfolgreich TYPE='S', Message (ID:/stzh/messages, NUMBER:000): "I:/stzh/messages:000 Beleg wurde erfolgreich gebucht", LOG_NO:, LOG_MSG_NO:000000 (PARAMETER:, ROW:0, FIELD:, SYSTEM:D70450)
2010-06-24 17:08:43 Erfolgreich BAPI erfolgreich ausgeführt
2010-06-24 17:08:43 Erfolgreich Commit-Transaktion mit BAPI_TRANSACTION_COMMIT
2010-06-24 17:08:43 Erfolgreich MP: Verlässt den Modulprozessor
2010-06-24 17:08:43 Fehler Zustellung der Message an die Anwendung über RFC_http://sap.com/xi/XI/System ist fehlgeschlagen weil: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired.. Message wird auf 'fehlgeschlagen' gesetzt
2010-06-24 17:08:43 Fehler Der Status der Message wurde auf FAIL gesetzt
2010-06-24 17:08:43 Fehler Rückgabe der synchronen Fehler-Message an rufende Anwendung: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired..
why does the rfc-adapter sends the bapi_transaktion_commit after an soap-error?
thank you for your help.
regards
t.

Sender JDBC to Receiver RFC scenario

Hi All,
I have to configure an scenario of sender JDBC to receiver RFC wherein SAP PI will be pulling data from third party database (Oracle).
Since I am configuring such scenario of sender JDBC, I want help on every important key aspects/prerequisites of configuring sender JDBC adapter/channel. I want to understand about Database Connection, Processing Parameters, etc. details while configuring sender JDBC channel and their significance/relevance.
Also I need guidelines about the source data structure (message type or external definition) to be used/created in ESR.
How sender JDBC channel and receiver JDBC channel differs from each other?
Please guide me on this.
Thanks & Regards,
Amit Patil

Hi Amit,
First of all you should read the sap.help documentation:
Configuring the Sender JDBC Adapter - Advanced Adapter Engine - SAP Library
Configuring the Receiver JDBC Adapter - Advanced Adapter Engine - SAP Library
Later, you can read Rajs's blog to advance concepts and perfomance JDBC Receiver scenarios best practices part-1
Finally, search the other blogs and documents in the SCN.
How sender JDBC channel and receiver JDBC channel differs from each other?
JDBC sender always does a poll to a DB table (with join some tables) in wich table you will need a field checkbox to mark the registers read, and the the receiver JDBC you can do a typical SQL construction like SELECT, INSERT, DELETE, etc. Both cases need the JDBC DB driver installed (check the SAP notes for this, also you can find some examples in the SCN:http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8000cffc-6b92-2d10-3493-f2ac1399242f?quicklink=index&… PI/XI: deploy a JMS/JDBC driver without JSPM? ).
Regards.

How to enable viewing of payload for receiver RFC adapter in RWB

HI All,
We can see the payload of all adapters in RWB by clicking on the message link under component >> adapter monitoirng. However when i click on message link for receiver RFC adapter, it does not show any payload. How can I enable this payload?
Regards

Hey
Sync messages are Cached rather than persisted in RWB to save memory.
You need to change the following parameter in Visual admin to see sync messages in RWB
Service SAP XI AF Messaging:
messaging.syncMessageRemover.removeBody = false
its set to True by default hence it does not stores the messages.
You may have to restart the Java stack after the changes (but first try without restarting the Java stack).
Thanks
Aamir
Pl:You will see the sync messages in Message Monitoring in RWB (not sure if it will show up in Communication channel monitoring as well)

RFC PROBLEM:NO DATA AVAILABLE IN ST03N

Hi experts,
On the t-code ST03 when i enter lastminute's load and confirm, getting the error RFC Problem:No data available.
How to go ahead.
From
Deepak Keesara.

Hi Deepak,
First thing you can check that job SAP_COLLECTOR_FOR_PERFMONITOR is runningby t-code sm37.
This job runs in client 000 under user ddic with periodic of one hour.
If not schedule it in t-code sm36
Login as user ddic to client 000 ,execute t-code sm36 give the job name SAP_COLLECTOR_FOR_PERFMONITOR, give abap program RSCOLL00 AND GIVE PIRIODIC VALUE ONE HOUR THEN SAVE AND RELEASE.
Regards
Ashok
Edited by: Ashok Dalai on Aug 18, 2008 1:20 PM

Receiver RFC Adapter

Hi All,
I am getting this error in communication channel monitoring for receiver RFC Adapter.
Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling Z_CRM_LEAD_CREATEMULTI in remote system (RfcClient[S10440_RFC_CallOutComes_Out]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Illegal move of the field symbol of a LOOP ... ASSIGNING.
Have gone through lots of links on SDN but not able to solve it out.
Any inputs will be greatly appreciated.
Thanks,
Venkat

Hi,
this one seems pretty simple
>>illegal move of the field symbol of a LOOP ... ASSIGNING.
this suggests that your error is inside FM Z_CRM_LEAD_CREATEMULTI
so correct the code (probably the table you try to loop is empty)
and try once more
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ

Getting the following error in receiver RFC channel

Hi Folks,
Iam having two RFC channels one as SENDER and other as RECEIVER.Ensuring that all the required data is perfectly given while creating these two channels...the SENDER RFC channel status is green in channel monitoring and RECEIVER RFC channel is red!
Iam gettiing follwing error against RECEIVER RFC channel -
<b>"Receiver channel 'Receiver_RFC' for party '', service 'BXT_100_IS'
Error can not instantiate RfcPool caused by:
com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or password is incorrect. Please re-enter"</b>
Even iam pretty sure about the user and pwd used in RECEIVER RFC channel...
and also i noticed "perform notification" status is failed in cache notification against my user id...
Can anyone help me in resolving this issue..
Thanks in advance..
Regards,
Ram.

Hi Ram,
Please change your password to UPPERCASE and try.
I have came across few instances where SAP converts passwords to uppercase while storing and so they dont match.
Hope this helps.
Regards,
Rahul.

Schedule Receiver RFC communication channel to call R3 RFC-FM.

Hi,
I have requirement that I need to schedule/trigger from PI to RFC call R3 function module. Wonder if anyone here has done similar thing before? I tried to use ATP (Availability time planning) in RWB. But this seem does not success for me as there is no response and error message for this.
Below is my configuration detail:
Configured:
1. Receiver communication channel - RFC
2. Receiver agreement with the RFC message type assigned.
3. Scheduled receiver RFC communication channel via ATP daily
*(It is possible to make scheduling job in R/3 but we are not considering this way)
Please let me know if anyone has done this before or any other suggestion to do the scheduling from PI.
Thanks!
Regards,
SP

Hi SP,
As you mentioned, ATP would allow adapter to be open and in start state. Adapter's RFC, SOAP, JMS would need some other application to trigger the message processing because these are not like pooling adapter's File, JDBC and Mail. RFC adapter channel always listening to the RFC port and FM execution. Once FM from R/3 executed then the RFC adapter would trigger it's message processing.
For Sender RFC channel: In order to trigger the RFC adapter execution at particular time then you should write a simple ABAP code which would act a batch application and which does the triggering the FM and Sender RFC channel.
For Receiver Channel: For Receiver RFC channel it's bit trichy because here you have force Receiver RFC adapter to connect backend the execute or initialize the variables without having any XI message triggered from Sender PI channel.
I have 2 ideas:
1. A little difficult approach, similar to the ABAPbatch code, you need to write a java adapter module which can trigger RFC receiver channel to connect and do an initialisation at FM at regular interval.
2. Simple approch configure a File-> 2-> RFC receiver scenario, configure File sender adapter to pick a dummy file at regular interval and RFC receiver channel does the rest.
Please let me know still you have any doubts,
Thanks,
RK

Receiver RFC synchronouse scenario question:

Dear All,
I have a doubt in Receiver RFC sync scenario. for example file to XI to RFC.
Question: when ever Response RFC is triggered in R/3 Side. How the data reaches XI.
By just creating Synch Communication channel for the RFC in XI, will the data to come to XI for RFC respose.
How when a Respose RFC is Triggered in R/3 Server, how the data points or reaches XI port?
How the Auto Triggered RFC Respose data points to XI and Comes to XI in a Synchronous RFC Receiver scenario.
PS: I am not from ABAP background. if any code has to be written in R/3 side for making the response RFC point to XI, please provide a generalized code also if possible.
Please Advice,
Prakash.

RFC destination,port at XI would help to get response data
No need to write any code,because RFC provide sync communication.
use links RFC Scenario using BPM --Starter Kit
https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
Exposing BAPI as Web Services through SAP XI
RFC Scenario using BPM --Starter Kit
The specified item was not found.
The specified item was not found.
HTTP to RFC - A Starter Kit

Configuring receiver RFC adapter to use RFC destination

Hello,
   I have been doing some digging, but I can't find a solid answer on how to configuring a receiver RFC adapter to use an existing RFC destination to call a 4/6C R/3 backend system... Our scenario is to WS --> SOAP --> RFC which is up and running in production just fine on NW 7.0, SP12.
   I ask this question because we, as a company, do not like to maintain passwords in multiple systems. That is necessary when we use the receiver RFC adapter now since SNC is a distant pipe dream for us and we would like to use an existing RFC destination that is set up to call the backend system using a logon ticket.
   I checked the relevant links I could find below, but I can not resolve the answer from them. Has anyone set this up successfully? This link (RFC Destination type RFC Receiver Adapter?) mentions it briefly, but it does not go into any length on how to set it up.
Thanks!
John
http://help.sap.com/saphelp_srm40/helpdata/fr/33/c6e63b60c25767e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
Re: Asynchronous RFC call

Hi John !!
I suggest you to create a new user, without dialog access in your ECC system to be used exclusively by the XI system to access ECC. And then, always use this user in all RFC receiver adapter communication channels.
Regards,
Matias.

RFC PROBLEM IN ST03

Hi experts
when executing the transaction ST03N it is executing in expert mode but when i click on Detailed analasys>Last Minute's Load>Total
right side i given all inputs like client no,user id and time after clicking enter it showing the below error
RFC problems:No data available
please any one help me urgently
Cheers
deepak

HI,
if you are using ECC 6.0 apply basis support package SAPKB70012
check Note 1032653 - ST03N "RFC problems: No data available"
if you already applied SAPKB70012 then apply following sap note
Note 1070989 - ST03N "Last Minute's Load" does not return any data
regards,
kaushal
Edited by: kaushal malavia on May 5, 2008 6:39 PM

Receiver RFC Adapter -Advance Mode option

Hi Experts
I want Execute the commite transaction after Trigeering the Standred BAPI through XI.
We haveAdvance Mode option in Reciver RFC Adapter . Any one explain me how to implment this.
Regards
Upendra.V
Edited by: upendra v on Jan 26, 2009 1:47 PM

Hmmmm.. I guess you are just practising & exploring all the featers of RFC.. isn't it?
Anyway upto what I know is here..
>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.
First of all you need to write an ABAP program in R3, there you will call your RFC/BAPI to update the database entries.
In XI, under your receiver RFC adapter check the box "Commit Handiling for Single BAPI Calls". Once you click you will get another check box called "BAPI Advanced Mode".
>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.
Once you send the data from XI to R3, then in R3 function module BAPI_TRANSACTION_COMMIT will be called explicitly (you need to define/call this BAPI after the ABAP code for database update). This will commit the work and return the result success or failur in a parameter called RETURN.
And after this BAPI you should call BAPI_TRANSACTION_ROLLBACK, so that in case of errors the transaction will be rolled back.
>The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values u201Cu201D, u201CSu201D, u201CIu201D, and u201CWu201D are displayed. All other values are regarded as errors.
As described above.
>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.
Once you check the box "BAPI Advanced Mode" a table will appear, there you can write your own values e.g.u201Cu201D, u201CSu201D, u201CIu201D, and u201CWu201D.
I can not provide a better solution then this... you have to do a work around, but above are the basic steps which can be considered before implementing the solution.
Regards,
Sarvesh

On ST03N "RFC problems: No data available"

Hi,
Can anyone tell me I am getting an error on T code ST03N as "RFC problems: No data available" when I am clicking on last minute load.
Checked the RFC it is working well.
Thanks
Hari Mohan

Hi Hari,
check whether below job running in your system.
SAP_COLLECTOR_FOR_PERFMONITOR
This job should run in client 000 under user DDIC with periodic of one hour.
The program is RSCOLL00
IF cancelled rerun it or if not scheduled sechedule it.
Regards
Ashok

RFC Receiver Adapter (Problem)

Hi All,
I have configured RFC Receiver Adapter : Here i have imported a Z FM for example
"" Z_API_DOCUMENT_CREATE_TEST "" having below import paramaters:
LF_DOCNUMBER     TYPE     BAPI_DOC_DRAW-DOCUMENTNUMBER
IV_PF_HTTP_DEST     TYPE     RFCDES-RFCDEST
IV_PF_FTP_DEST     TYPE     RFCDES-RFCDEST
LF_FILENAME     TYPE     BAPI_DOC_DRAW-DOCUMENTNUMBER
1) Now i use MM to fill in two parameters : LF_DOCNUMBER , LF_FILENAME
If my FIle is of kind : test55.pdf     --> LF_DOCNUMBER = test55
                                                       LF_FILENAME       = test55.pdf
For this i have checked in Sender File Adapter "Adapter Specific Message Attributes"
So i write UDF to capture Filename and Filename with extension to fill above shown parameters.
Now i saw target xml after mapping in CC monitor of RWB is as below
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Z_API_DOCUMENT_CREATE_TEST xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
<IV_PF_FTP_DEST>SAPFTPA</IV_PF_FTP_DEST>
<IV_PF_HTTP_DEST>SAPHTTPA</IV_PF_HTTP_DEST>
<LF_DOCNUMBER>xierror</LF_DOCNUMBER>
<LF_FILENAME>xierror.doc</LF_FILENAME>
</ns0:Z_API_DOCUMENT_CREATE_TEST>
But LF_FILENAME is getting populated to my Z FM at runtime but LF_DOCNUMBER works fine filling up with value.
But when i run the FM using F8 it works , what could be the problem.
Any advice
regards
Srinivas

Hi,
The problem is with the Data types used for LF_DOCNUMBER.
Make this as Char or Numeric in FM and then try. If its of any packed values then conversion will create the problem
Thanks
Swarup

Receiver RFC Problem

Similar Messages

Maybe you are looking for