on 03-04-2008 1:14 PM
Hi All,
I have Simple file to file transfer.
There are text files at source side that need to send at receiver side.
Source text files name are different so I have used
Adapter Specific Attributes for Sender and Receiver Adapetrs
Question
As these are text files and there is no mapping required what interface name should I give at Sender Aggrement and
at Interface Determination.
Pls describe steps
Regards
HI Rider,
think this helps you
Steps:-
In IR
1) Create a data type (X_DT), Message type (X_MT),
2) Create 2 Message interfaces for same Message type, one is IN_ASYNC (X_MT_IN_ASYNC)and other is OUT_ASYNC (X_MT_OUT_ASYNC).
3) Create a Message Mapping (X_MM) (No need to map anything here) just call same Message type for Source and Target (X_MT).
4) Create Interface Mapping(X_IM). give the two Message interfaces here and give the MM and Message Type.
In ID
1) Create a Sender Communication Channel and Reciever Communication Channel.(provide the Content Conversion as Required)
2)Create Reciever Determination :- use outbound Message Interface as sender interface(X_MT_OUT_ASYNC here)
3) Create Interface Determination :- user outbound Message Interface as sender interface(X_MT_OUT_ASYNC here) and give Inbound Message Interface as Inbound Interface (X_MT_IN_ASYNC)
4) Create Sender Agreement: Call the Sender CC : Give sender interface as (Out_ASYNC)
5) Create Receiver Agreement:Call the Reciever CC Give Reciever interface as (IN_ASYNC)
There may be better approches than this, but it worked for me.
Regards,
Sukarna Chirumamilla.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If your source and the target message strucures are same, then u dont require mapping. otherwise u need mapping
Otherwise if you wont bother abt the output message at target side means u can traansfer the data with out IR Developement
Regards
Seshagiri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Service has to be a valid business service or system in the ID.
Interface name can be anything you make up, but should be unique. In this case, it is "nonexistence_interface".
Namespace name can be anything you make up or already exists. In this case, it is "http://abc.com".
/people/william.li/blog/2006/09/08/how-to-send-any-data-even-binary-through-xi-without-using-the-integration-repository
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
I do not want to use file conversion from txt format to
xml format.
I simply want to transfer my text file from source side to target side in (txt format)
If I go by this blog
/people/william.li/blog/2006/09/08/how-to-send-any-data-even-binary-through-xi-without-using-the-integration-repository
In Receiver determination I am getting this error while configuring Receiver
"Message interface does not exist in any software components installed on this business system"
Pls advice
Hi All,
I am going by this blog
/people/william.li/blog/2006/09/08/how-to-send-any-data-even-binary-through-xi-without-using-the-integration-repository
In Receiver determination I am getting this pop up while configuring Receiver:
"Message interface does not exist in any software components installed on this business system"
I clicked ok and do the configuration as given in blog
When I send data in sxmb_moni I get error message
"No receiver could be determined" -- do not know why?
Regards
Hi,
Try this Method to avoid the error
"Message interface does not exist in any software components installed on this business system"
1) Open ID-----Double click on Business system that which u are using in the scenario
2) Check whether you are able to see the SWC in the Othere attributes TAB
3) If it is not there means goto SLD----Open the Technical System of R/3 by choosing Web as ABAp type
4) Click on Installed Products TAB
5) Click on Add New product and add your Product of the SWC whcih you are using for developement and Save it
6) Then goto Business systems TAB in the same Technical systems window and click on the Business System appears in the window.
7) Click on Installed products and Check the check box of your Product and then finally save that.
Now you should be able to see the SWC in the Othere attributes TAB in ID
Regards
Seshagiri
Hi All,
I am going by this blog
/people/william.li/blog/2006/09/08/how-to-send-any-data-even-binary-through-xi-without-using-the-integration-repository
When I send data in sxmb_moni I get error message
"No receiver could be determined" -- do not know why?
Steps I have done
Sender Aggrement
Service -- BSV_FILE_SENDER
Interface -- nonexistence_interface
Namespace -- http://CRM
Sender Comm Channel -- File_Sender_CC
Receiver Determination
Service -- BSV_FILE_SENDER
Interface -- nonexistence_interface
Namespace -- http://CRM
Configured Receivers
Service -- BSV_FILE_REC1
Interface Determination
Service -- BSV_FILE_SENDER
Interface -- nonexistence_interface
Namespace -- http://CRM
Receiver
Service -- BSV_FILE_REC1
Configured Inbound Interfaces
Inbound Interface Namespace
nonexistence_interface http://CRM
When I send data in sxmb_moni I get error message
"No receiver could be determined" -- do not know why?
Hi Raj,
Now I have created a new business service -- File_BSER
with both sender and receiver comm channel in that service
I am getting the error below and I am not able to see
my message in sxmb_moni.
When I see in message monitioring I am getting below error
Received XI System Error. ErrorCode: INBOUND_BINDING_ERROR ErrorText: ErrorStack: Error in sender agreement for party , service File_BSER, interface namespace http://CRM, interface nonexistence_interface No sender agreement found for ..."
How to solve it
Regards
Rider,
Its very simple scenario. For ur satisfaction I did the same, it's working perfectly. I don't know what mistake u did. Let me give the complete picture.
Step1: Create new Scenario
Step2: Create new Business Service, let say File_BusService
Step3: In File_BusService add the outbound and Inbound Interface name and namespaces , like
Outbound Interface: MyInterface
Outbound Interfacenamespace: http://my-own-namespace.com
Inbound Interface: MyInterface
Inbound Interfacenamespace: http://my-own-namespace.com
Step4: Create two communication Channels under File_BusService
Step5: Receiver Determination.
Sender:File_BusService
Outbound Interface: MyInterface
Outbound Interfacenamespace: http://my-own-namespace.com
Configured Receivers
File_BusService
Step6: Interface Determination.
Sender:File_BusService
Outbound Interface: MyInterface
Outbound Interfacenamespace: http://my-own-namespace.com
Inbound Interface: MyInterface
Step7: Receiver agreement
Receiver Service: File_BusService
Inbound Interface: MyInterface
Receiver Comm.channel
Step8: Sender Agreement.
Sender:File_BusService
Outbound Interface: MyInterface
Outbound Interfacenamespace: http://my-own-namespace.com
Sender Comm.channel.
raj.
"As these are text files and there is no mapping required what interface name should I give at Sender Aggrement and
at Interface Determination."
Interface name at sender agrement? select the outbound intefac you have created just give the name as MI_FIle_outbound or somethign similar
for interface Determination slect the Inbound interface which you have created for inbond and MM leave it blank.
( for this you will not create the interface mapping in IR)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you have to cofnigure an file adapter to do an File content conversion and use that in Sender agrment...this will take care of the TXT fiel converting into XML.
dnt wory abot large file jut check the strucutre you have...post the file strucutre and data tyope you have build will help u configuring the adapter.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
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.