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.

Similar Messages

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

Doubt regarding ALE SETTINGS in IDOC scenario.

Hi Friends,
        I have some doubts regarding ALE settings for IDOC scenarios, can anyone please clarify my doubts.
For exmaple take IDOC to FILE scenario
The knowledge i got from SDN is --
One need to do at the R3 side is --- RFC DESTINATION (SM59) for the XI system.
                                                   --- TRFC PORT for sending IDOC to the XI system
                                                   --- CREATING LOGICAL SYSTEM
                                                   --- CREATING PARTNER PROFILE
               at the XI side is --- RFC Destination ( For SAP sender system)
                                       --- CREATING PORT for receiving IDOC from the SAP sending system(IDX1).
1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
In IDOC to IDOC scenario-------
2. Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
3. If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
y we r creating receiver communication channel in the case of FILE to IDOC scenario?
4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                FILE to IDOC scenario,
IDOC to IDOC scenario individually.
Thanks in advance.
Regards,
Ramana.

hi,
1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
it is a mandatory step in doing ALE configurations
2. We create 1 RFC destination each in R3 and XI.
    R3 RFC destination points to Xi and
    XI RFC destination points to R3
3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
4. ALE settings for all IDOC scenarios are same as follows....
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful
Prashant

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

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

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

Have some doubt regarding the weblog (Lookup's in XI made simpler)

Hi All,
I have created the same scenario as mentioned in Siva's weblog (Lookup's in XI made simpler).
I having some doubts regarding the scenario, it will be great if you help me to resolve the same.
I am having a file-file scenario where I need to do lookup in database(MS-Access) through mapping.
The standard file-file scenario is in place and in addition I have created a receiver jdbc channel . I have also created the receiver agreement for the same in the cofiguration.
While creating the receiver agreement you have to specify the interface name which includes the message typeI have specified the normal format which we specify while configuring the jdbc receiver adapter.
In the message mapping I have created a advance user defined function as mentioned in your weblog which calls my receiver jdbc channel.
I have also specified the select query to be executed in the mapping program.
While testing I am getting the following error
Cannot produce target element /ns0:Role_MT/URole. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
<b>Can you please suggest me what all I need to do in addition to the file-file scenario for this lookup scenario to work.</b>
Thanks and Regards
Rahul

Hi,
Following is my user defined function
//write your code here
String Query = "";
Channel channel = null;
DataBaseAccessor accessor = null;
DataBaseResult resultSet = null;
Query = "Select URole from Lookup where UName = ' " + UName[0] + " ' and UPassword = ' " + Pwd[0] +" ' ";
try{
channel = LookupService.getChannel("DB_service","JDBC_channel_receiver");
accessor = LookupService.getDataBaseAccessor(channel);
resultSet = accessor.execute(Query);
for(Iterator rows = resultSet.getRows();rows.hasNext();){
Map rowMap = (Map)rows.next();
result.addValue((String)rowMap.get("URole"));
catch(Exception ex){
result.addValue(ex.getMessage());
finally{
try{
if (accessor!= null) accessor.close();
catch(Exception ex){
result.addValue(ex.getMessage());
Thanks and Regards
Rahul

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.

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.

Basic doubts Regarding the RFC to File scenario.

Similar Messages

Maybe you are looking for