ALE

[Former Member]

Hi,

Is it Possible to send an IDOC from a Sending System to

two different systems?

[Former Member]

Hi,

Is it Possible to send an IDOC from a Sending System to

two different systems?

[Former Member]

Hi Santosh,

Yes it is possible.

The only requirement is partner profile should be appropriately configured.

In the distribution model u can also specify filters for each receving system.

To set up an ALE connection u can visit following link.

http://help.sap.com/saphelp_erp2004/helpdata/en/78/217d6851ce11d189570000e829fbbd/frameset.htm

Hope it'll help u.

Thanks & Regards,

Ankur

[Former Member]

Hi Ankur,

If you look at FM RECIPIENT_GET_FROM_ALE_MODEL, it gives an error message if more than one recipient are found!!

How to avoid this?

[Former Member]

Hi Santosh,

I have checked the FM RECIPIENT_GET_FROM_ALE_MODEL in where used list and it is used only in 1 report.

Could u elaborate more about ur issue .

Thanks & Regards,

Ankur

[Former Member]

Hi,

This FM RECIPIENT_GET_FROM_ALE_MODEL is used in RSNASTED in the routine ALE_processing.

I have this requirement....

I need to send Dilveries from SAP system to another Non-SAP System.

I have Configured this in Distribution model and Partner profile.

Apprantly, Some one else have already configured to send Dilveries to some other system from the same logical system which I am using.So now from the same sender there are two reciptients.

When I run RSNAST00 it fails in the FM RECIPIENT_GET_FROM_ALE_MODEL with the error message

too many reciptients.....

Please help!!!

Thanks,

Santosh

[Former Member]

Hi Santosh,

This is a known limitation of ALE, when we faced the same situation we used EDI as the communication medium instead of ALE. EDI medium (subroutine EDI_PROCESSING of report RSNASTED) does not have this limitation. Maybe you can try using EDI medium to solve your problem. You need to define processing routine (mentioned above) for medium EDI in output configuration (Txn. NACE).

Cheers,

Sanjeev

[Former Member]

I've logged an OSS message to have this looked at. We have the same issue in version 5.0.

[Former Member]

This message was moderated.