Outgoing Proxy to XI 3.0 failing "unexpected value S; A was expected"

[Former Member]

Hi All,

I have a problem where my outgoing async proxies are failing with the following error.

Error: Attribute ProcessingMode has the unexpected value S; A was expected

I had this problem at another client and we used the following notes to fix it.

1609041 - XI runtime: Synchronous acknowledgements

1849533 - XI runtime: synchronous acknowledgments II

1857701 - XI runtime: Synchronous acknowledgements III

we implemented the notes on PI and it fixed the error, the only problem I have is that these notes are for SAP_BASIS 7.0 and higher see below.

Currently on this client I am using XI 3.0 so my SAP_BASIS is 6.20, so I can't implement these notes on XI.

Anybody have some advise for me?

Regards,

CJ Bester

[Former Member · Accepted solution]

Hi,

The Problem has been resolved.

SAP has extended the notes to XI as well, so if anyone else has this problem
implement the notes on XI.

1609041 - XI runtime: Synchronous
acknowledgements

1849533 - XI runtime: synchronous
acknowledgments II

1857701 - XI runtime: Synchronous
acknowledgements III

And then Implement this one on SAP ECC

1849533 - XI runtime: synchronous
acknowledgments II

Regards,

CJ Bester

[Former Member]

Hi,

Try to check the "Adapter-specific Identifiers" or your used business system. If this isn't filled correctly you'll get the above error.

[Former Member]

Hi, I have remove the Technical system and Business system, regenerated the Technical system recreated the Business system on the SLD, and then deleted the business systym on the integration directory and re-imported it from the SLD and I still get the same error.

[Former Member]

Hi Bester,

The Adapter specific identifiers of the Business system can still be wrong or empty when to regenerate the objects themselves.

See Adapter-Specific Identifiers - Integration Directory - SAP Library

This will give you more information where you can find the Adapter specific identifier and what it does.

Resume: Go to Integration Builder -> Affected Business system -> Communication Component -> Adapter specific Identifiers and check the filled parameters or reimport them from the SLD.

[Former Member]

Hi,

I did that as well and the problem is still there.