Problem Executing RFC to File Scenario

Hi,
I am currently working on RFC to File Scenario which is Asynchronous in Nature i.e. The RFC will send some data to XI and then it'll be dumped in an XML File on the shared drive.
Following are the steps which were performed by me :
1. i created an RFC Destination in R/3 using SM59 and entered the Required values as mentioned in the blog
The specified item was not found.
2. Then i entered the same values in the communication channel of the sender RFC adapter.
I tested it from R/3 and the connection was successful.
3. i created an RFC in SE37 in the R/3 and just added an existing table under the "tables" tab. No further code was written in it. I saved it and activated it.
4. All the IR and ID objects were made and activated and then the scenario was run by sending a single data row by pressing F8. The RFC showed a message of "System Failure" and while looking into the XI Server (SXMB_MONI) the message gave absurd values with a error symbol(it a Red Light symbol and there was no Red Flag).
Initially, the XML file was getting posted in the shared drive but after further execution it stopped.
I am unable to figure out the problem. Kindly let me know where i am going wrong and what needs to be done to correct it ?

Hi,
For Sending RFC asynchronously check for these points:
For RFC creation and importing please follow this discussion. Very useful:
Re: RFC to FILE
Specially reply by Udo Martens.
Also for sender RFC, check two things.
1) First step is Register your ProgramId using activiating the communication channel(XI). You should be able to see it in smgw(R/3)
smgw->Goto->Looged on Clients(Check it here)
2) Then use this registered programid in your RFC Destination,in R/3 (it is Case-Sensitive).
These are just common errors i have encountered sometimes.

Similar Messages

Facing problem with RFC to File scenario

Hi Team,
My scenario is like this:
Iam running a report in r/3 system which would then create a file on target side.
I am taking source message as external definition.r/3 people have created proxy on sender side(r/3 server).
when i run the report it would then call proxy and send data to xi.
when i run report on r/3 end it is generating succesful msg in moni.but iam file is not getting created on file server side(iam using NFS file server).
RWB is showing status as holding.not able to tarce out the problem exactly.
Kindly help me out.
Regards
Madhu

i have gone through the link but still unble to resolve the error.
could help me out with more solutions?
Regards
Madhu

Issue in File to RFC to File Scenario with BPM using Block Step

Hi Everybody,
                       I am doing File to RFC to File Scenario for multiple records using BPM using Block Step. The File Message is getting posted and after that, the message is getting stuck up in the qRFC Monitor (Inbound Queue).
                    After seeing the message in Inbound Queue, I am trying to execute and release the message. But when i execute the LUW, it says " Function module doesnt exist or EXCEPTION raised" in Inbound queue.
Could somebody suggest me the outcome of this? What does this mean and how to
release the stuck up message in Queue.
Thanks and Regards,
N.Jayanth Kumar

Hi Rajesh,
                       After going through the blog, i saw the trace messages. It says
" The   exception occurred (program: CL_SWF_XI_INBOUND=============CP, include CL_SWF_XI_INBOUND=============CM00F, line: 19)"
Regards,
N.Jayanth Kumar

RFC destination for RFC to File scenario

Hi,
I m creating a TCP/IP RFC destination in R/3 system for my RFC to File scenario.
Step 1:
For this a Registered server program is created in Jco RFc Destinations with,
Program Id : pgm1
Gateway host : PI's host
Gateway service : PI's service
application server host: ECC's host
system numer     : ECC's number
client : ECC's client
logon user : ECC user
password : pwd
Step 2:
In SM59, TCP/IP connection the following parameters are given:
Program ID : pgm1
Gateway host : PI's host       -
> is this correct
Gateway service : PI's service      -
> is this correct
Step 3:
So i am calling the RFC in ABAP program (R/3 system) like:
CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'
Step 4:
In PI side,
for RFC sender I am passing :
Application server : PI server
Application server service: PI host
program ID: pgm1 which was created in the previos step
For RFC Metadata Repository Parameter, i am passing all the values related to R/3
Please let me know whether the steps and values i given is correct.
B'cos even if i give ECC's information in Gateway host and Gateway service the scenario works fine and if i PI's info then also it works fine.
so i am confused as which is the correct method. pls clarify

Ok I will try to explain....
Assumptions: R3_TO_XI is the name of RFC which I created in ECC of type T.
While creating the RFC in ECC we mention a unique name which is called Progaram ID. Now the same program id we mention in our sender RFC CC.
So now when an ABAP Progarm (where you will call this RFC with it's destination) is scheduled/triggered with the code as mentioned below then since the DESTINATION ('R3_TO_XI') mentioned here contain the same program id which we have mentioned in our sender CC, invokes the adapter in PI and soon after that all pipeline steps get executed in XI.
CALL FUNCTION 'ZBAPI_COMPANY_GETDETAIL'
IN BACKGROUND TASK
DESTINATION 'R3_TO_XI'
TABLES
    comp_detail = company_detail.
COMMIT WORK.
Regards,
Sarvesh

Error Handling on RFC - XI - File Scenario

I have an R/3 RFC -> XI -> FILE scenario that works, but does not adequately handle the error of my R/3 to XI connection being down.
The RFC call is async since I was under the impression that I had to do a "to file" scenario that way.
    CALL FUNCTION 'ZXO_SAP2RFC'
      IN BACKGROUND TASK
      DESTINATION wa-rfc_dest_1
      EXPORTING
        request          = request
        rfc_header       = rfc_header.
    COMMIT WORK AND WAIT.
    IF sy-subrc <> 0.
      [error handling]
If my rfc destination is down (for example when XI is down), this RFC call is still getting a sy-subrc of '0' (so my error handling does not kick in).
Any suggestions?

Hi Keith,
your scenario is working correctly. If XI is down you will find your message queued in transaction SM58, where you can restart it manually. Usually there should be standard job for report RSARFCEX, which is periodicly trieing to restard the message.
Asynchr Call (tRFC) means that your program continues completly undependent from that call.
Make a test: Change temporary the called machine in SM59 destination to senseless value and execute your programm. Your message should be in SM58. Then correct the destination and wait a few minutes...
Regards,
Udo

CC error in RFC to File Scenario

Hi ,
While am trying to do end-to-end test for a RFC to file Scenario. Am getting this below error. Please help me to proceed further.
Could not process due to error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value '2008-08-13' too long (>8 for 2. column) - must stop', probably configuration error in file adapter (XML parser error)'
Regards,
Hemanthika

Hi,
Please go through this Blog
RFC Scenario using BPM --Starter Kit
check this blog on how to configure sender rfc adapter.
The specified item was not found.
I hope it helps,
Regards,
Surya

Triggering RFC FM in R3 for the RFC to File scenario

Hi All,
I am Developing a RFC-XI-FILE scenario where i am unable to triger an RFC from the source system(R/3) .I have used the RFC-FM : ZBAPI_COMPANY_GETDETAIL ( which is remote enable) i havent written any source code in the function module : just i have created only the parameters in the table as :
Tables:
COMPANY_DETAIL LIKE T880
i have created a source code in the se38 of R/3 to call this function module as :
DATA: COMPANY_DETAIL TYPE STANDARD TABLE OF T880 with header line .
selection-screen begin of block blk1 with frame title text-001.
PARAMETERS : COMP_ID TYPE BAPI0014_2-COMPANY.
selection-screen end of block blk1.
start-of-selection .
SELECT RCOMP
       NAME1
       CNTRY
       LANGU
       STRET
       CITY
       FROM T880
       INTO CORRESPONDING FIELDS OF TABLE COMPANY_DETAIL
       WHERE RCOMP = COMP_ID.
CALL FUNCTION 'ZBAPI_COMPANY_GETDETAIL'
               IN BACKGROUND TASK
               DESTINATION 'SENDRFC'
TABLES
    COMP_DETAIL = COMPANY_DETAIL.
COMMIT WORK.
I have created RFC destination in R/3 as : SENDRFC of type T with the programid : SENDRFC_PORTAL this same program id is used in the XI sever for the sender RFC adapter .
When i execute the above program in R/3 the changes are reflecting in the XI when i checked in the SXMB_MONI.
Please sugest the correct source code if the above source code is wrong and provide me the exact process to do .
Regards,
Bharat .

Hi bharat,
>>When i execute the above program in R/3 the changes are reflecting in the XI when i checked in the SXMB_MONI.
That means your RFC was called and the data was sent to XI.
>>Please sugest the correct source code if the above source code is wrong and provide me the exact process to do .
Since XI was called the source code is correct.
Am I missing something here? Can you provide some details about your requirement/error.
Regards
Suraj

Issue in RFC to File Scenario

Hi All,
I am working on SAP PI 7.31 dual stack. I have configured a simple RFC to File scenario with aysnchronous interface. I am using classic configuration.
In Sender RFC channel monitoring I am getting the below exception and the file is not created.
"Error in processing caused by : com.sap.aii.af.lib.mp.module.ModuleException : call to messaging system failed: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message xxxxxxxxxxx(OUTBOUND) expired".
Please suggest me what could be the issue.
Thanks,
Madhurima

Hi Madhu
As the log says the function module is try to execute synchronously.
But as per your requirement it should be asynchronous. Please remove all the export parameters from the function module.
Then re-import the function module in PI and adjust mapping and operation mapping.
Stop and start the RFC sender adapter so that it will get the new metadata of the function module.
The function module should have only import parameters so that it will act like a asynchronous interface.

RFC to File Scenario..

All,
Quick question - im trying to configure a RFC to file scenario. Is there a step-by-step document somewhere. I did the steps as mentioned in few of the blogs (Michal's and others) and im kind of stuck in how to trigger the scenario?
Thanks.

Hey thezone,
you can make it like this:
- create a "dummy" RFC, which is a function module with enabled remote access. In this dummy RFC, there should be no source code, only importing parameters (and these importing parameters are the ones you'll see in request message when importing the RFC into Integration Repository);
- create a RFC Destination of type T (TCP/IP) in SM59. Then, select it as "Registered Server Program" and use some string for the ProgramID field (best practice is to use ProgramID = RFC Destination name). Finally, enter hostname and gateway of RFC Server (which can be the same as of the web as abap where you have these objects). Gateway should be "sapgwXX" (with no quotes), where XX is the System number;
- this rfc should be called by the function module which is executed by your report. In the function module, use it like this:
    CALL FUNCTION '<rfc_name>'
      IN BACKGROUND TASK
      DESTINATION <rfc_dest_name>
      EXPORTING
where <rfc_name> is the name of the dummy rfc, <rfc_dest_name> is the name of the RFCDestination you created, and you export the parameters expected in Importing Parameters field of the dummy RFC;
- Import the dummy RFC in Integration Repository and use it for relevant mappings/interfaces;
- Finally, in Integration Directory, when creating the Sender RFC Adapter, Program ID should be the same of the RFC Destination you had created in SM59 of source system, and hostname/gateway should also be the same you inputed there.
Regards,
Henrique.

RFC to File scenario.. Messages not available in sxmb_moni

Hi Experts,
I have created simple RFC to File scenario in my sandbox system. First time I am doing this type of scenario.
When I execute the program which is created to call the RFC Function Module nothing is coming into sxmb_moni in sap system as well as in PI system. I don't know why messages is not coming to sxmb_moni.
Please suggest me how to resolve this issue.
Thanks & Regards,
Satish Kumar P.

Hi Satish,
first monitor Sender RFC channel in communciation channel monitroing ,after executing program in ECC if BAPI triggered then definely you will see log in RFC sender channel.
if nothing was found then prob in ECC side like Pogram triggered BAPI.
Regards,
Raj

HTTP-RFC(BPM)-FILE Scenario

I have a problem on using the 'http-RFC(BPM)-File scenario'. When i enter values using the Client http adapter, it displays message telling that "BPE_ADDAPTER.SYNCHONOUS_MESSAGE"
The error msg is displayed below:
Result:
<SAP:Error>
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code>BPE_ADAPTER.SYNCHONOUS_MESSAGE</SAP:Code>
<SAP:Stack>The process does not support the given synchronous interface or does not support synchronous messages</SAP:Stack>
</SAP:Error>
Also in SAP XI monitor, the sender services along with the corresponding sender interfaces.
Expecting this prob will be off soon.
thanks
vinod v

Hi Vinod,
your process is asynchronous (no sync async bridge). But you send "Quality of Service = Best Effort" (Url paramater qos=BE). You should send "Exactly Once" (EO).
Regards,
Udo

NO DATAS IN OUTPUT FILE FOR RFC TO FILE SCENARIO

In RFC to File scenario, I am executing the ABAP program in ECC and generates a empty file in PI server.
I am getting the error message in SM58 of ECC:
u2018Bean Z_HR_OUTBOUND_DATA2 not found on host SDNPI1,u2019
'call FM Z_HR_OUTBOUND_DATA2 to ProgId ECCTOPI_OUTBOUND on host SDNPI1 wit'
RFc Source code:
FUNCTION Z_HR_OUTBOUND_DATA2.
""Local Interface:
*" EXPORTING
*"     VALUE(FILENAME) TYPE BBP_ACC_DESCRIPTION-ACC_OBJ_NAME
*"     VALUE(RETURN) LIKE BAPIRETURN STRUCTURE BAPIRETURN
*" TABLES
*"      ITAB10 STRUCTURE YSTRING1 OPTIONAL
*"      P_STATUS STRUCTURE ZHRT0031 OPTIONAL
DATA : wa_status TYPE zhrt0031,
         wa_itab10 LIKE ITAB10.
break-point.
LOOP AT p_status INTO wa_status.
    CONCATENATE wa_status-pernr
                wa_status-ename
                wa_status-orgeh
                wa_status-plans
                wa_status-persg
                wa_status-rank
                wa_status-***
                wa_status-icnum
                wa_status-usrid
                wa_status-dept
                INTO wa_itab10-str1.
    APPEND wa_itab10 TO itab10.
ENDLOOP.
wa_itab10-str1 = 'test'.
append wa_itab10 to itab10.
append wa_itab10 to itab10.
    CONCATENATE sy-datum
                'PYO_EMPDAT.TXT'
                  INTO
                  filename.
ENDFUNCTION.
And in the ABAP program the RFC is called like:
CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
in background task destination 'ECCTOPI'
EXPORTING
INTERFACE       =
IMPORTING
   FILENAME        = filename
   return = return
TABLES
   ITAB10          = itab10
   P_STATUS        = p_status
When i am testing the standard program STFC_CONNECTION in ECC with the same RFc destination it works fine and creates a o/p file with the datas in it, but if i m executing the other function module it doesnt contain any data it.
What could be the error? and how to resolve the errors that i am getting in SM58?
Thanks

Bean Z_HR_OUTBOUND_DATA2_1 not found on host SDNP1, ProgId =ECCTOPI_OUTB
Change the case of your Program ID to lower ecctopi similar was the issue in this thread:
Bean ZFM_MODULE_OUT not found on host <XI_HOST>
And may be for the same reason even Michal used lower case program ID in his blog.
Regards,
Abhishek.

Rfc to file scenario error in sm58

rfc to file scenario error in sm58
i get the error as com.sap.aii.afccommunication.RfcAfwException
:look up of alternative

hey
>>i have a doubt do we have to use
starting new task or back ground destination
well it depends upon the logic ur gonna implement,both are used for async RFC so u have to see ur requirement and then decide.
have a look at the following
http://help.sap.com/saphelp_nw2004s/helpdata/en/22/042578488911d189490000e829fbbd/frameset.htm
thanx
ahmad

Removal of Namesapce from generated target file in RFC to file Scenario

I am working on RFC to File Scenario. In target file we are getting the target namespace also. we need to remove it from the target file but how?
Thanks
Anuj Agarwal

Anuj,
Go to the Message Type you have created for your File.
You will see a field called Namespace. Just remove this / Delete this , and activate your message type.
Relaod the message type in the message mapping and now the namespace will not occur in the target.
Regards
Bhavesh

Basic doubts Regarding the RFC to File scenario.

Hi All,
I'm doing a RFC to File scenario, so before starting the development i went through many blogs and sites to know more the about scenario. I'm confused in the step where we have to create a RFC (type TCP/IP) in sm59.
I have the following doubts :
1)whether to create the RFC in sender (which will be ECC system) or XI.
i.e., RFC in sender (ECC) pointing to xi system in sm59 of Sender(ECC)
or
in XI pointing to sender (ECC) system.
2) the program id maintained in RFC.
the program id is any name or the FM which is being imported in XI system.
Thanks in Advance,
Kind Regards,
Lalitkumar.

Hi Lalitkumar,
1)whether to create the RFC in sender (which will be ECC system) or XI.
i.e., RFC in sender (ECC) pointing to xi system in sm59 of Sender(ECC)
or
in XI pointing to sender (ECC) system.
It should be in sender ECC.
2) the program id maintained in RFC.
the program id is any name or the FM which is being imported in XI system.
It can be any name but should be same in RFC destination and RFC adapter.
As stefen mentioned use ABAP proxy inspite of RFC as its better performance wise.
Regds,
Pinangshuk.

Problem Executing RFC to File Scenario

Similar Messages

Maybe you are looking for