on 01-05-2007 6:17 AM
Hi,
I need to Configure a Scenario in such a way that when i Execute RFC the Output should be Sent to File by using XI.
Configuration Done by me.
Imported RFC. Created a File Data type, Message Type, Inbound Asyn Message Interface, Created an Outbound Message interface for RFC Response. Done Message mapping and Interface mapping.
Created Sender Aggrement,Receiver Aggrement,Receiver Determination,Interface Determination also.
when i execute the RFC from Abap Report. it is throwing an Error
"senderAgreement not found: lookup of binding via CPA-cache failed for..."
So i created an Sender Aggrement as
Service: SAP Business System
Interface: RFC name
Namespace: urn:sap-com:document:sap:rfc:functions
it gave new Error that No Receiver Determination.
So can Any one say
How can i do Message and Interface Mappings for this since RFC is Sync and File is Asyn?
If i create an Message Interface with RFC and File in Syn Mode it is giving an Error
"Message interface Message Interface Bapi_File_Abs_Syn | urn:
test8_RFC references an RFC message and a non-RFC message"
So please Suggest Me How to Create this Scenario.
Thanks in Advance.
Sriram
Hi Sriram,
I am sorry to have to say that none of the replies to your question so far is right.
Do not create a message interface for RFC, use the imported RFC for routing and mapping.
When you have an async RFC, so you just map the request, there is no response tab, when the target is async.
Regards
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Steps:
1. Import the RFC to your Integration Repository
2. Create a DT, MT and MI for the file side of the interface.
3. Create MM from RFC Request to MT of file. Please test the Mapping
4. Create IM
Do the configuration on the Integration directory.
Please do not create any MI for the RFC. Then name can be used as MI.
Regards
Vijaya
Hi,
Just do the below steps,
Imported RFC.
Created a File Data type, Message Type, Inbound Asyn Message Interface - these are all for Response
Create the Message Mapping BAPI.Repsonse to Response Message type which is created you.
Create the Interface Mapping Source is Directly select the BAPI Target is Inbound Async interface (BAPI you can use ASYNC/SYNC)
Created Sender Aggrement - Sender R/3 Busines system , Interface is RFC , RFC Namespace and Communcation channel
do the rest all steps...Receiver Aggrement,Receiver Determination,Interface
Above all the steps i tried i am geeting some DeliveryException error..i am finding the solution how to resolve that also..
Don't create for the Source Outbound Interface..directly use BAPI.
Regards,
Venu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Create the Interface Mapping Source is Directly select the BAPI Target is Inbound Async interface (BAPI you can use ASYNC/SYNC)
How can u Select Reponse type Directly - Directly select only BAPI That's all.
(BAPI_COMPANYCODE_GETDETAIL - Source Interface)
Create the Message Mapping - BAPI.Response Source Target is your Message type. (Once Drag the BAPI you will see three message types select Second one BAPI.Response)
I did same thing...
Regards,
Venu.
Sriram,
You would need to create 2 Message Interfaces , both of them ASYNCH.
Create the Message Interface for RFC --> Otound Asynch and use the RFC request as the corresponding message Type.
Create the Message Interface for File --> Inbound Asynch.
Create 1 message mapping between the RFC request message and the File message type
Create 1 interface mapping ( between the Asynch Message Interfaces ).
Make sure that you have 1 sender agreement ,. 1 receiver determination, 1 receiver agreement and 1 intreface determination.
Also, make sure that only one sender RFC adapter uses the program id used in the TCP IP connection.
Regards
Bhavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
first: Is your scenario File -RFC- FILe
In this case your file data will be mapped to the Import of the RFC and then response fromt he RFC will be mapped to another file strucutre. so yes you need BPM
Second: RFC to file as mentioned in the first statement. Here the import of the RFC will be mapped to the MT of the file. no response mapping done.
You have to call RFC in the ASYNC mode.
So are you trying to do either of these scenrios
Regards
vijaya
Hi,
The concept of RFC is that you send the data in the import and hte RFC gets executed in the remote SAP server and gets the response to the sender system.
In case where you are using SAP XI or any middleware when you do a RFC to file scenario, what you are actually doing is just using RFC as a container to send the data:
In RFC to file scenrio, the Import or the Request of the RFC is to be mapped to the file Message type and not the response.
Hope this helps.
Regards
vijaya
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.