RFC Receivers in the Communication Channel

[Former Member]

I created, within an XI scenario, an RFC Receiver object in XI that has the ALE Remote User ID and password to connect to a specific environment that grabs idocs and puts them into files (Outbound from R3 to XI). However, I noticed when I did this another Reciever object for that same environment, not within this scenario, was active with the wrong password. When running this process we got error mesages that the process could not log into the environement.

Question: If more than one RFC Receiver is setup to log on to a specific R3 environment, say two of them, if only one is in the scenario, shouldn't it only point to the one in the scenario. Thus, if a second RFC Receiver is setup, but not in the scenario, shouldn't it be ignored? It seems like it will still trying to use the RFC Receiver that was not in the senario.

Thank-You.

[Former Member]

Hi Tom,

your problem sounds like business logic.

From a XI point of view, business logic has to be in the backend system. This is your R/3.

Try to find some logic (e.g. lock database, taht is read by your rfc).

If the database is locked, the secons rfc should not go on with processing.

Regards Mario