Genrate Proxy Inbound as Synchronous or Asynchronous

[Former Member]

Hi Expert,

We have current proxy inbound Asynchronous which generated from XI (determione mode as Asynchronous with identify fault message type) since 2 years ago.

When I hit regenerate in SPROXY for that inbound message, it will generate as synchronous proxy, and the code in Asynchronous is gone.

Anyone know why?

When I remove fault message type, it will generate as Asynchronous. Why?

Cheers,

Nattawat

[deepak_shah]

Hi,

SProxy wont generate synchronus proxies for an asynchronous interface. There should have been some change in your interface for sproxy to generat sync proxies.

Also As when inbound proxies are regenerated the abap code written with the method will be removed.

So a better approach will is to write the code in the function module so that even if proxies are regenerated the Code still remains in function module.

Please refer to following link:

/people/michal.krawczyk2/blog/2007/04/29/xipi-abap-proxies--keep-them-clean

Regards,

Deepak.

Edited by: Deepak Shah on May 6, 2010 4:08 PM

[Former Member]

> When I hit regenerate in SPROXY for that inbound message, it will generate as synchronous proxy, and the code in Asynchronous is gone.

Why are you regenerating the proxy? Have you done some changes in your interface (Data type Structure change or message interface change).

First check if you or someone else has done some changes in your message interface. Because this could be the reason your asynchronous proxy code is getting disappeared.

[Former Member]

Yes, I have done some change on message interface in XI, but I have not changed the mode (the mode is still Asynchronus) and fault message type is still there. When I regenerate SPROXY, it will generate as Synchronous mode.

But when I delete fault message type, and regenerate it again, it will generate as Asynchronous.

Why fault message type is related to Synchronous or Asynchronous mode, when generate the SPROXY?

Before that I used to generate SPROXY as Asynchronous mode when there is a fault message type declare.

[Former Member]

I am not really sure why this is happening.

Have you recently upgraded your R3? Or applied some notes. If yes then this could be happening because of some side effects.

You can also have a look into this blog may be it can help you..

/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1

What you can do is, after adding the fault message activete your interface and clear the cache and then try to re-generate the proxy again.

[stefan_grube]

I asume that somebody changed the message interface in Integraton Repository.

Here you define whether the proxy will be sync or async.