Multiple clients, same sys id

I have a situation where I would like several SAP clients with the same system IDs (on different hosts) to address the same AD service (on a single java host). The problem of course that is the connection FP_ICF_DATA_<SID> can only address one client. Is it possible to use proxy settings in the RFC connection on the SAP client in this situation? any other ideas?

Amit,
Thanks for your reply. Perhaps my problem is not clear. I have 5 different 'T02' SAP ECC systems (I use the word 'client' here in the context of client/server, not the SAP client sense). Each one is on a different host server, say hpriap23, hpriap24, hpriap25 etc. I have 1 java system on a different host (say hpriap55). In the ICF destination in NWA of the java system I have FP_ICF_DATA_T02 (there can only be 1) and it refers back to a host/port for the ADS client - for example http://hpriap23:8023.
I don't see how the ICF destination can be used for the SAP T02 system on hpriap24 (for example) ?
Perhaps you can explain your circumstances.
Thanks,
Guy

Similar Messages

Multiple-client, same server, different configurations

Hi experts,
Recently we have got a project of IS-U Electricity where it has been planned that the same server we used for the last project will be used for this upcoming project where the configurations are diffrent from each other but both of them will run together in same development, quality and production servers.
My question is whether we would be able to configure sap as per the requirements for the upcoming project to a particular client whereas the rest of the clients will use old configurations for the existing project in the same server. Will there be any cross-client configuration conflicts?
- Arghya

Arghya:
The answer to this question is unrelated the industry solution. Multiple client scenarios are used in many solutions. Some configuration is client dependent and so would be different in each client; other configuration is client independent and would be used in all clients. That would be part of the analysis to determine if multiple clients or multiple systems is the correct approach.
regards,
bill.

WSUS Multiple clients, same name...different IP Addresses

I am deploying WSUS 3.0 SP2 into a lab environment. I have 6 duplicate networks. Duplicate up to the IP address that is. They all use the same names for their systems, by the IP's are different. For example, their are six differnt
machines named "Client 1", but they all have 6 DIFFERENT IP addresses. In my WSUS console, I can get the machines to show up, but it looks like the machines with the same name are being seen as the same device despite the different IP addresses.
Is there a work around for this?

but it looks like the machines with the same name are being seen as the same device despite the different IP addresses.
Is there a work around for this?
Since you have six entries for 'Client1' it would not likely be a SusClientID issue. The machine name and IP Address are attributes of the SusClientID (a GUID). If you have six visible entries for 'Client1', then you have six unique SusClientIDs for those
systems.
Your real issue is the reuse of the hostname. You need to have UNIQUE machine names within a single enterprise network if you want to use WSUS.
Are these "6 duplicate networks" all WORKGROUP-based environments, or are you using Active Directory in each network?
If they're all workgroup-based networks, then you're going to have to change the machine names.
If you're using Active Directory, then it may be as simple as (which really ain't all that simple) -- changing the Domain Name of each network so each 'Client1' is in a different domain, and thus has a different FQDN (e.g. client1.domaina.local, client1.domainb.local,
etc.)
You might also be able to achieve this just through DNS services even if they're still a workgroup. Configure the DNS suffix for each network via the DHCP Server, so that each network uses a different DNS suffix, which will be reported to the WSUS server
and uniquely identify each machine by FQDN.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Product Manager, SolarWinds
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

Accessing the same stateful session bean from multiple clients in a clustered environment

I am trying to access the same stateful session bean from multiple
          clients. I also want this bean to have failover support so we want to
          deploy it in a cluster. The following description is how we have tried
          to solve this problem, but it does not seem to be working. Any
          insight would be greatly appreciated!
          I have set up a cluster of three servers. I deployed a stateful
          session bean with in memory replication across the cluster. A client
          obtains a reference to an instance of one of these beans to handle a
          request. Subsequent requests will have to use the same bean and could
          come from various clients. So after using the bean the first client
          stores the handle to the bean (actually the replica aware stub) to be
          used by other clients to be able to obtain the bean. When another
          client retrieves the handle gets the replica aware stub and makes a
          call to the bean the request seems to unpredictably go to any of the
          three servers rather than the primary server hosting that bean. If the
          call goes to the primary server everything seems to work fine the
          session data is available and it gets backed up on the secondary
          server. If it happens to go to the secondary server a bean that has
          the correct session data services the request but gives the error
          <Failed to update the secondary copy of a stateful session bean from
          home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
          to the primary server will not reflect changes made on the secondary
          and vice versa. If the request happens to go to the third server that
          is not hosting an instance of that bean then the client receives an
          error that the bean was not available. From my understanding I thought
          the replica aware stub would know which server is the primary host for
          that bean and send the request there.
          Thanks in advance,
          Justin


          If 'allow-concurrent-call' does exactly what you need, then you don't have a problem,
          do you?
          Except of course if you switch ejb containers. Oh well.
          Mike
          "FBenvadi" <[email protected]> wrote:
          >I've got the same problem.
          >I understand from you that concurrent access to a stateful session bean
          >is
          >not allowed but there is a
          >token is weblogic-ejb-jar.xml that is called 'allow-concurrent-call'
          >that
          >does exactly what I need.
          >What you mean 'you'll get a surprise when you go to production' ?
          >I need to understand becouse I can still change the design.
          >Thanks Francesco
          >[email protected]
          >
          >"Mike Reiche" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Get the fix immediately from BEA and test it. It would be a shame to
          >wait
          >until
          >> December only to get a fix - that doesn't work.
          >>
          >> As for stateful session bean use - just remember that concurrent access
          >to
          >a stateful
          >> session bean is not allowed. Things will work fine until you go to
          >production
          >> and encounter some real load - then you will get a surprise.
          >>
          >> Mike
          >>
          >> [email protected] (Justin Meyer) wrote:
          >> >I just heard back from WebLogic Tech Support and they have confirmed
          >> >that this is a bug. Here is their reply:
          >> >
          >> >There is some problem in failover of stateful session beans when its
          >> >run from a java client.However, it is fixed now.
          >> >
          >> >The fix will be in SP2 which will be out by december.
          >> >
          >> >
          >> >Mike,
          >> >Thanks for your reply. I do infact believe we are correctly using
          >a
          >> >stateful session bean however it may have been misleading from my
          >> >description of the problem. We are not accessing the bean
          >> >concurrently from 2 different clients. The second client will only
          >> >come into play if the first client fails. In this case we want to
          >be
          >> >able to reacquire the handle to our stateful session bean and call
          >it
          >> >from the secondary client.
          >> >
          >> >
          >> >Justin
          >> >
          >> >"Mike Reiche" <[email protected]> wrote in message
          >news:<[email protected]>...
          >> >> You should be using an entity bean, not a stateful session bean
          >for
          >> >this application.
          >> >>
          >> >> A stateful session bean is intended to be keep state (stateful)
          >for
          >> >the duration
          >> >> of a client's session (session).
          >> >>
          >> >> It is not meant to be shared by different clients - in fact, if
          >you
          >> >attempt to
          >> >> access the same stateful session bean concurrently - it will throw
          >> >an exception.
          >> >>
          >> >> We did your little trick (storing/retrieving handle) with a stateful
          >> >session bean
          >> >> on WLS 5.1 - and it did work properly - not as you describe. Our
          >sfsb's
          >> >were not
          >> >> replicated as yours are.
          >> >>
          >> >> Mike
          >> >>
          >> >> [email protected] (Justin Meyer) wrote:
          >> >> >I am trying to access the same stateful session bean from multiple
          >> >> >clients. I also want this bean to have failover support so we want
          >> >to
          >> >> >deploy it in a cluster. The following description is how we have
          >tried
          >> >> >to solve this problem, but it does not seem to be working. Any
          >> >> >insight would be greatly appreciated!
          >> >> >
          >> >> >I have set up a cluster of three servers. I deployed a stateful
          >> >> >session bean with in memory replication across the cluster. A client
          >> >> >obtains a reference to an instance of one of these beans to handle
          >> >a
          >> >> >request. Subsequent requests will have to use the same bean and
          >could
          >> >> >come from various clients. So after using the bean the first client
          >> >> >stores the handle to the bean (actually the replica aware stub)
          >to
          >> >be
          >> >> >used by other clients to be able to obtain the bean. When another
          >> >> >client retrieves the handle gets the replica aware stub and makes
          >> >a
          >> >> >call to the bean the request seems to unpredictably go to any of
          >the
          >> >> >three servers rather than the primary server hosting that bean.
          >If
          >> >the
          >> >> >call goes to the primary server everything seems to work fine the
          >> >> >session data is available and it gets backed up on the secondary
          >> >> >server. If it happens to go to the secondary server a bean that
          >has
          >> >> >the correct session data services the request but gives the error
          >> >> ><Failed to update the secondary copy of a stateful session bean
          >from
          >> >> >home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
          >> >> >to the primary server will not reflect changes made on the secondary
          >> >> >and vice versa. If the request happens to go to the third server
          >that
          >> >> >is not hosting an instance of that bean then the client receives
          >an
          >> >> >error that the bean was not available. From my understanding I
          >thought
          >> >> >the replica aware stub would know which server is the primary host
          >> >for
          >> >> >that bean and send the request there.
          >> >> >
          >> >> >Thanks in advance,
          >> >> >Justin
          >>
          >
          >

We have created shared folder on multiple client machine in domain environment on different 2 OS like-XP,Vista, etc. from some day's When we facing problem when we are access from host name that shared folder is accessible but same time same computer when

Hello All,
we have created shared folder on multiple client machine in domain environment on different 2 OS like-XP,Vista, etc.
from some day's When we facing problem when we are access from host name that shared folder is accessible but same time same computer when we are trying to access the share folder with IP it asking for credentials i have type again and again
correct credential but unable to access that. If i re-share the folder then we are access it but when we are restarted the system then same problem is occurring.
I have checked IP,DNS,Gateway and more each & everything is well.
Pls suggest us.
Pankaj Kumar

Hi,
According to your description, my understanding is that the same shared folder can be accessed by name, but can’t be accessed be IP address and asks for credentials.
Please try to enable the option below on the device which has shared folder:
Besides, check the Advanced Shring settings of shared folder and confrim that if there is any limitation settings.
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

WDS 2012 R2 - Cannot PXE multiple clients at the same time

Hello All,
This is my first post on here so I apologize if this is the wrong place. I work for a school district and we are implementing WDS 2012 R2. We've been extremely satisfied with the speeds and ease of use through unattend files. However, for
the past month I've been looking for a possible answer to a problem that has plagued us from day one of implementation.
So here's the problem:
I have a stand alone WDS server which is not a domain controller and is not our DHCP server. I have IP helpers and broadcast forwarders setup on the network. As well as option 66 and 67 in DHCP. So far so good right!
Well that's partially right. When we boot one client at a time to the WDS server. Everything works as intended. We can TFTP the necessary files from the WDS server. Everything boots up and we're off and running.
However, if we boot up two or more clients at the same time. The WDS server never responds to the traffic. The clients get their DHCP information. They start the referral and download from the WDS server, but get no response. I'm
really hoping that someone on here would have some insight of something I can try. I've about exhausted my list of peers and contacts. They're all stumped as well and were smart enough to stay with 2008 WDS.
I would prefer to stick with 2012 R2 since it's setup and working for the most part. With only this one hiccup.
Thanks in advance for any guidance!

Hello Daniel,
I appreciate the reply and apologize for taking so long to get back to this. Things have been a little hectic over here.
I have tried everything on this forum and I am still unsuccessful in PXE booting multiple clients at the same time.
Multicast is enabled on the server, and it works for the clients. However, as stated in the original post. I cannot boot multiple machines at the same time. I can start them from the image selection screen around the same time though. So,
that appears to be working fine.

Multiple clients with same account on a single IMAP server

Hi,
I am connecting to a IMAP server using same account but from 2 different machines. From one machine a mark a message as SEEN=FALSE. But on the second machine, the flag will still be TRUE.
Is there any way to co-ordinate between multiple clients so that all the clients are in sync.
Regards,
Nitin.

I was able to resolve the problem using addMessageCountListener and messagesAdded method, as suggested by you.
I am now facing another problem. Whenever a new message is received, code inside messagesAdded method gets executed. Here I am trying to spawn another thread and do some stuff. But this new thread is not starting at all. It goes into some JavaMail:EventQueue and does nothing. What is the concept of EventQueue here? How can I get this new thread executed?
Also will there be synchronization problems in messagesAdded method. Say I received a message and I am processing it in the messagesAdded method. In the mean time another message comes up. How will this behave.

How to use multiple clients within JCO?

Hi,
I'm pretty new to configuring Web Dynpro's with it's JCO connections. I have the following question.
We are using one portal (SAP EP 6.0_640 SP15) and one R/3 system (SAP ECC 5.0) with multiple clients (multiple customers who are all using the same portal).
Do I have to deploy a web dynpro for each client and maintain it's JCO connection for each client?
Or is there another way how I can set this up?
Thanks in advance.
Kind regards,
Dave Arends

Hi Dave,
<b><i>Do I have to deploy a web dynpro for each client and maintain it's JCO connection for each client?
Or is there another way how I can set this up?</i></b>
You dont need to deploy a web dynpro for each client . You can use same JCO connection for multiple User ID's ( multiple Clients mean multiple user ID's on the same portal ).
If this is the case then single JCo connection is enough to pull data from R/3 and show on portal page .
Thanks,
Nanda

How to control one server with multiple clients via TCP/IP

I am wanting to control a single server with multiple clients. Only one client would be active at a time, so there would be no conflict. I want to use TCP/IP. So far, I have programmed a cluster that passes data back to the server with no problems. The challenge come in when a second client is added to the mix. I have't been able to figure out how to turn each client on and send the appropriate data and then turn it off so it doesn't keep sending the same data to the server.
Here are the things that I have considered and did some preliminary testing, but don't really know how to impliment:
1. Send a numeric on the front of the cluster packet that tells the server that data is on the way.
2. Send a boolean on the front of the cluster packet to somehow turn the server TCP/IP on.
The problem I have found is that LabVIEW TCP/IP doesn't like to be turned on and off. If it doesn't get the data it expects, it goes into a reset mode and that kills the response time.
Any help?

You should consider implementing a set of simple one-byte commands that can be sent back and forth between the Server and the Clients. You can base all of these ideas off the example in the Example Finder under Networking >> TCP and UDP called Multiple Connections - Server.
You will have two loops in the server VI: one to wait for new connections, and one to send and receive data from the existing connections. For instance, after one of the clients connects, it can request control of the server to send data to it by sending the character "R" for request. Every time the send/receive loop of the Server executes, the first thing it can do is to check all the existing connections to see if any of the clients have sent a control request ("R"). If so, it will create a buffer (array) of control requests. This could be in the form of Connection IDs or indexes in the array for a particular Connection ID. Your choice.
After the Server receives a request for contol, if it is not already under control by another client, then it can send a response to the first client on the control request list. For instance, the server could send the first client a "S" command for send. Note that after the clients send their control request, they should execute a TCP Read and wait indefinitely for the server to respond with the one-byte "S" command. Then, once the client in control is finished sending data to the server, it could send the character "X" telling the Server to release it from control.
The example I mentioned above already does a similar thing. Note how when a client wants to disconnect, they send the letter "Q". You can see this in the Multiple Connections - Client VI. The Server then checks each individual connection to see if it's received this one-byte command, and if it has, it closes the connection to the client. This is what you would want to implement, but instead of having just one command, you'll have to distinguish between a few and build up a buffer of control requests.
Finally, if a client does decide to disconnect in your application, they could send the command "Q" just like the example above. At this point, close the connection and remove that Connection ID from the array of connections. You will also have to handle the case that this client was in the request control waiting line when it disconnected, in which case you need to delete it from that array as well.
This will definitely work for you, but it will take some work. Best of luck!
Jarrod S.
National Instruments

What are the possible approches for hosting a product(custom SP application) for multiple clients on a single SharePoint farm?

We have a product which is a custom application based on SharePoint Foundation 2010. Right now, for each of our client we create a dedicated server and host the application in the standalone deployment. Now, the requirement is to host multiple clients in a
farm deployment.
Challenges are: 1. The product has same name for the wsp that is deployed on different client servers as of now. How to distinguish for different clients on same farm
Currently the product specific css and jquery is in 14 hive. These files will be of difefrent versions for different client. How to segregate that?
How many web applications is recommend to be created in a single SPF 2010 farm? What are the challenges?
There are a couple of DBs created in SQL for the application. What is the best way to separate those for the client?
Essentially its the same product but with different versions for each client that we want to deploy in a single farm. What is the best practice to tackle this?

For the most part, these are not SharePoint questions per se, but product-specific questions you'd better ask the vendor about. To get in some more detail:
1. It totally depends on the scope of the solution. If its global, then you're out of luck and any changes you make affect all instances that use it. Better ask the vendor about it.
2. Not that many, let's say < 10, assuming you're web applications have separate application pools. Check out http://technet.microsoft.com/en-us/library/cc262787(v=office.14).aspx#WebApplication for
more info.
3. This is very application specific and really should be answered by the vendor. Not related to SharePoint at all.
4. Again, really depends on the product so better ask the vendor.
Good luck!
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

Is it possbile to have multiple clients on our Production instance

We have our Production system with client 101
Our abapers want me to create another client 500 (config only - not easy to accomplish) to be used for our Mexican users.
I told them to create another company code for Mexico, but they do not know how to do this.
DO I have any other options, of yes
Pros and cons of having multiple clients in same production instance.
I know that any independent code is going to effect all clients.
THanks
Joe

Hi Jo,
you CAN create a new client, but mostly this is not done, because the effort to maintain multiple clients is mostly higher than just different company codes. Yes, ABAPs are client indpendent and therefore valid for all clients.
So, the argument, to "not know" how to create different company codes is not valid to me !
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Multiple clients on socket connection

Hi!
I understand that it is possible that multiple clients listen to one server (on the same port) and even write to it (then it should be a multi-threaded server).
But i would like to refuse connectios, if one client is connected. How can I do that?
In my case I have a (single threaded) server. Now one clients connects. The server waits to receive data from the client and answers, without ever closing the port. that works.
Now if I connect with a second client, the openicng of the socket in the second client works fine, although the server does not seem to notice the second client. Communication is not possible between the server and the second client, and the server doesn't answer to the first client anymore, although he receives data from it.
So, since the server does not seem to notice the second client (does not accept the connection) and I don't get an exception at the second client, what can I do?
Thank you for your help!
concerned Code (if you want to take a look at it):
CLIENT:
socket = new Socket(hostname, echo_port);
SERVER:
try
ServerSocket waitingsocket = new ServerSocket(echo_port);
try
     socket= waitingsocket.accept();
     System.out.println("Client connected");
     ReaderThread reader = new ReaderThread( this, socket );
     reader.start();
catch (Exception e)
READER:
public void run()
     while (true)
          try {
               int bytesRead = inStream.read(inputBuffer,
               0, inputBuffer.length);
               readCallback.tcpUpdate(inputBuffer,bytesRead);
          catch (Exception oops)
               readCallback.tcpUpdate(null,-1);


Just to make sure this is clear: You can NOT have multiple clients on a given socket connection. You CAN have multiple clients connected to a particular port on a given server, but each client will be communicating with the server through a different of socket.
The usual approach here is to set up a listening ServerSocket on the desired port, call accept() on it, then process the communication from the returned Socket object. This is usually done by spawning a new thread and allowing it to handle the socket communication, while the ServerSocket loops around to another accept() for the next communication.
Here's an excellent intro to the concepts (the code is really ugly and poorly implemented, but it does a good job of explaining the overall concept). I used this as a starting point, and now (after a whole lot of development) have a pretty sweet extensible web server class that handles template expansion, etc... (I use this as a quick and dirty UI for some of my apps, instead of requiring the user to install a JSP container):
http://developer.java.sun.com/developer/technicalArticles/Networking/Webserver/
- K

How to handle multiple clients with DatagramSocket

I am trying to handle multiple clients with 1 datagramSocket bind to one port (basically I have only one port to use, and I can not use TCP or any other ports). At the server side I have two threads one for receiving packets and buffering them, another for processing the packets in the buffer and sending replies.
I can have multiple clients sending datagramPackets to me and I will have to process the packets and send them to DIFFERENT clients. Ex. Client 1 sends datagramPacket to Server which sends the processed packet to Client 2. Also Client 2 sends a datagramPacket to Server which again processes the packet and sends it to Client1. May have Client 3 and 4 doing the same thing at the same time... and so on...
My root class is creating the datagramSocket(somePort) and two threads (receiver and sender). How can I use the socket that I created in these two threads??
I have done the following and I am getting "java.net.bindexception". When I am sending stuff from Client1 to Client2 everything is fine but when I start sending something from Client2 to Client 1, I get the bindexception... Client 1 is using port 3000, Client 2 is using port 4000.
I really don't have a lot of experience in socket programming so I am not sure if there is a much simpler way to do this. I appreciate all the tips and help that I can get...
Thanks...
class UDP_serv
     static DatagramSocket udpSocket;
     final static int SERVER_PORT     = 2000;
     public static void main(String[] args) throws SocketException
          udpSocket= new DatagramSocket(SERVER_PORT);
          new DataReceiver().start ();
          new DataSender().start ();
     static class DataReceiver extends Thread
          DataReceiver()
               Thread.currentThread().setName("DataReceiver");
          public void run()
               while (true)
                    byte pckt[] = new byte [MaxMsgSize];
                    DatagramPacket dp = new DatagramPacket (pckt, pckt.length);
                    try
                         udpSocket.receive (dp);
                         //PUSH TO RECEIVE BUFFER
                    catch(Exception e)
                         e.printStackTrace();
     static class DataSender extends Thread
          DataSender()
               Thread.currentThread().setName("DataSender");
          public void run()
               while (true)
                    processDataMsg();
      static void processDataMsg()
         DatagramPacket op;
         InetAddress DA = null;
         int DP = 0;
         byte [] outPacket = null;
         // POP FROM RECEIVE BUFFER
         // SOME PROCESSING HERE
         // Set Destination Address (DA)
         // Set Destination Port (DP)
         // DA and DP are the forwarding IP and Port addresses
         // not the addresses original packet was sent from.
         try
          op = new DatagramPacket (outPacket, outPacket.length,DA, DP);
          udpSocket.send(op);
         catch (IOException e)
          e.printStackTrace();
}Also for development and testing purposes, I am running the two clients and the server on the same machine (windows xp-32b) so all of the Destination IP Addresses are 127.0.0.1. and as I said Ports that I am using are 2000, 3000, 4000 (Server, Client1, Client2).

Hmm I have minimized the code and it seems to be working now.
I think I have an error in the header portion of the data I am sending, where I am storing the source IP/Port and destination IP/Port. I think the server in the middle is messing these values up while sending them to the destination Client. Because the destination client actually receives the stuff and sends the reply back to the server, but the reply packet's headers has 0/0 as the dest IP / Port...
Server is giving me java.net.BindException: Cannot assign requested address error when it tries to forward the reply it received from the client2 as the address it is trying to send is 0!
I guess it doesnt just give this error when you try to open two sockets to the same port...
Paul, Thanks for the direction on how to proceed... took me a while get the minimized code but at least figured out the problem. Well still have to make sure that is THE problem though :)
As far as the statics goes how can I change those to non static ones? Where do I make an instance of the top level class that creates the threads? and how do I pass the DatagramSocket to the threads/ if I dont need to pass how do I call or use the datagramSocket I created in the top level class? I mean do I still kinda have it like a global variable on the top?? A very simple example would be much appreciated...
I think these might be really basic questions but I am having a rough time with the hierarchy in java...

Multiple Clients in SCM 7.0

Dear All,
Can we have multiple clients in SCM 7.0?
What is pro's and con's of having multiple clients???
Thanks,
Siva.

Hi Siva,
For non BI-based applications such as PP/DS you can use multi-client landscape in the same manner as in ERP system.
For DP, SNP etc. see sapnote 522569 (it's relevant for 7.0 as well)
Regards,
Alexander

Multiple client receivers

Hi Experts,
I have a requirement where the SENDER is SOAP and the receiver is RFC.
Sender send the data and it should be bifurcated to 6 clients based on some condition.
Previously I have created a rule in receiver determination to send the date to multiple receivers which are existed in the same client.
But now here they want to send the data to multiple client receivers based on the condition.
Do I need to create the CC and receiver agreement for each receiver or is there any other option available ?
Please help me out with this.
thanks and regards,
praveen

Hi praveen,
Yes. You can handle this in the same way by creating the condition in Receiver determination.
But here you need to create separate Interface determination and receiver agreement for each receiver. You can use existing RFC Communication channel in Receiver agreement.
Regards
Baskaran K

Multiple clients, same sys id

Similar Messages

Maybe you are looking for