Proxy Error

[Former Member]

Hi,

When I send data from SAP ECC 6.0 to PI 7.0 using a proxy I get a very strange error message:

No implementing class registered for the interface (ABAP interface, request message MI_PROXY_FUST, request message, namespace urn:ecc:telers:fust)

I think this kind of message is relevant for inbound proxies. I'm using an outbound proxy.

When I look into sxmb_moni I see 2 lines for 1 proxy:

• One is "Inbound Message (Sender)"

• One is "Inbound Message (Receiver)"

Both lines are referring to the same message and the Second One is showing the problem.

I don't understand where this line with Receiver is coming from.

In the development environment this is not occuring.

Might the system landscap cause a problem:

1 installation

SAPECC client 400

SAPECC client 500

PI client 550

Flow of message is

client 400 --> client 550 --> file

Best regards

Ron

[Former Member · Accepted solution]

Hi,

Check the RFC destination defined for your Integration Server - it sounds like this is defined incorrectly.

Post what this is set to and I will see if I can see any issues.

Cheers

Colin.

[Former Member · Accepted solution]

Hi Colin,

The config is as follows:

On ECC Client 400

trx SXMB_ADM --> Integration Engine Configuration

Role of Business System: LOC Application System

Integration Server: dest://PRD_PROXY CONNECTION

trx SM59

RFC Destination: PRD_PROXY CONNECTION

Type of Connection H

Target Host <servername> Servicenr 8000

path prefix /sap/xi/engine?type=entry

Regards

Ron

[Former Member]

Hi,

Sometimes you get these messages due to name conflicts also.

Check the names and regenerate or activate again and make a syntax check.

Regards

Krish

[lnirmala]

Hi Ron,

Regarding the two lines for the same proxy in SXMB_MONI...this happens even in my QA environment also.It is not an error but since both ECC and PI are installed in the same machine two messages are appearing.

Rgds,

Lekshmi.

[Former Member]

Hi,

The second line RECEIVER is in error and the data is not created. Is this the same case in your systems?

Ron

[Former Member]

Found the problem.

In the SM59 http connection no SAP Login details were specified!!

In SXMB_MONI two lines are still displayed.

Ron

[former_member200962]

In the development environment this is not occuring.

So now is the scenario being tested in Quality or Production system? In this case can you confirm that the proxy is transported properly in the respective environment and is active.

Role of Business System: LOC Application System

The configuration seems to be fine.....i hope you are referring to the SXMB_ADM of the R3 system and not in XI/ PI

Regards,

Abhishek.

[Former Member]

Hi Abhishek,

In regard to your questions:

• In DEV it worked OK. In PRD it didn't. I already retransported the ABAP proxy to PRD (so it is completely generated again) The problem still occurs.

• yes I'm refering to SXMB_ADM in ECC back end system.

Ron

[Former Member]

You might want to check SAP Note 1147445 if you have an operation name thats different from the service interce name. This situation threw a similar exception in one of the scenarios I worked upon

[Former Member]

Hi Preety,

I checked the note and this one is not relevant for out system. I can not implement it.

Ron