Unable to convert the sender service to an ALE logical system

[former_member301120]

Hello,

I've read all threads dealing with this problem, but no suggest solved my problem.

In my case the sender service is a integration process. In the receiver agreement I activated header mapping.

Sender service is my XI system (XIPCLNT100 for this there is an entry in SLD). I thought this would solve my problem, but it didn't.

Thanks for your help.

Regards Christian

[former_member301120]

Hello,

I've found the problem. In Idoc-Receiver channel, the flag "restore origin partner for aknowledgement".

The messages were triggered by report "SXMB_REFRESH_ADAPTER_STATUS".

By the way, is there a need to trigger these aknowledgements?

In our R/3 backend they won't be processed.

Regards Christian

[Former Member]

Hi,

I just wanted to confirm the solution to that problem,

In Idoc-Receiver channel, was the flag "restore origin partner for aknowledgement" checked and unchecking the same solved your problem?

Regards,

Suddha

[former_member301120]

Hi,

no you have to check the flag "restore origin partner for aknowledgement" in order to solve the problem.

Regards

[santhosh_kumarv]

Hi,

Check in the SLD if the correct logical system is assigned to the R3 Business System.

By Michal Krawczyk

Thanks

SaNv...

[Former Member]

Hello,

The problem occurs when sender and receiver business system or business service does not have a logical system name.

ID - Integration Directory

Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.

Check this blog :

Regards

Gangaprasad

[former_member301120]

Hello,

at receiver system there is an entry at adapter specific indentifieres (IDOC-Receiver). Is there a need to create a own business system in sld for the sender service (the integration process)?

Regards

[prateek]

Is there a need to create a own business system in sld for the sender service (the integration process)?

No.

Check if the logical system name provided in SLD for business system of R3 is same as that present in Adapter Specific Identifier.

Regards,

Prateek

[former_member301120]

Hello,

yes the entry at adapter specific attributs is correct. It's the same as it is maintained in SLD as logical system name.

Regards

[Former Member]

Hi,

If you have not created a business system for your own business service in SLD; you can manually input any logical system name for this service directly as adapter specific identifier for this service. This value will be used by the IDoc adapter. In the IDoc Comm Channel remember to set the "Apply Control Record Values from Payload" indicator.

Additionally if you want to specify the Sender System in IDoc Control record from mapping - in the IDoc adapter set the indicator : "Take Sender from Payload".

And in the mapping map SNDPRT with constant "LS" and "SNDPRN" with what ever sender system value you want to specify for the sender partner number. Remember to make adjustments in the Partner Profiles for this Sender in the Receiver R/3 system.

Hope this helps.

Regards,

Suddha

[Former Member]

I think after doing lots of things you should also try with updating the cache by tcode sxi_cache and also clear the sld cache data from environment menu in you ID.

Just cross check few things like..

1. The name which you are selecting in you Receiver Agreement in header mapping is same as defined in logical systems at R/3 side by using tcode BD54.

[prateek]

Initially, the sender must be some system other than XI. Open the Business System/Service. Goto Services -> Adapter Specific Identifier, and check whether u have provided the correct logical system name there.

Regards,

Prateek