Skip to Content
0
Former Member
Feb 22, 2011 at 02:47 PM

Problems with the RFC eccat connections...

33 Views

Hi,

In our company we create a new development system named PBP, this system have the same system id as our production system named PBP too..

The recording ecatt process is executed in another development system that we have named DBP... but for some reason when we execute the ecatt process from DBP to our development system PBP the process take the IP address of our PBP production system and not the PBP ip address of our development system... I check the RFC that are using and the RFC are assigned with the PBP development IP so is correct...

The rare thing is that when we execute the ecatt the process automatically creates lots of RFC connections in the transaction SM59 automatically with the PBP production ip address and I don't know why the ecatt are working in this way because in the SECATT configuration I choose the RFC that is assigned to PBP development... not PBP production...

Some of you have gone through this problem before?

Thanks for the help!!

Carlos