on 04-20-2006 3:09 PM
Can we have more than one TRFC port for tranferring data from one logical system to another?
The requirement is to transfer same basic idoc type from one logical system to another through two different ports. Is it possible?
For eg. some specific data (country specific) for the same basic idoc type can be sent through a separate port and the other data through a different port inorder to distinguish between the two.
Hi Shital,
The port is referred in the communication channel, the communication channel in the receiver determination. You have there no condition, only an inbound interface, which is found in interface determination (also by condition). But in both cases you need to use the same inbound interface (your idoc), so i dont see a solution by this way.
To distinguish i would recommed to use different partner numbers. U have to develop a mapping, which fills the fields SNDPRN / RCVPRN of the IDOC and a headerfield mapping in Receiver Agreement on Sender Party / Receiver Party with X-Path.
Regards,
Udo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Udo
Thanks for the reply.
In this case there is only one partner system from where the data is coming, so we cant distinguish them on that basis.
Cant we develop two different RFC destinations between the two system and use two different ports for them. Then is it possible to send specific data (country specific) through a dedicated RFC destination and port number?
Hi Shital,
I don't think so. Because of that what i told you. There would be a dirty trick (back routing) to solve your issue. But its quite difficult and not standard. You create two http receiver services and two http sender services. You route your message depending on payload to the one or the other http receiver channel. The receiver is in both cases: THE XI! Now you have a second message, which you can route to IDoc adapter. But in this case you have different sender and in the receiver determination you can put the sender, so you will be able to use different communication channnels and so different ports / destinations.
Advantage: Your task would run, no performance problem (http: very good, asynchron)
Handicap: You see every message double in the monitoring, the scenario is not easy to understand and it is a big task 4 other people to change it.
Regards,
Udo
User | Count |
---|---|
94 | |
11 | |
11 | |
10 | |
9 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.