BD64 Dist Model - Filter for order type

[Former Member]

Hello experts,

I have two distribution models which both use message type ORDRSP. As I get the error "Too many recipients found for message type ORDRSP in the ALE model" I created a new filter object for field auart of table vbak in BD95. I added this new filter object to the segment E1EDK14 in BD59 of message type ORDRSP. Now in BD64 I assigned the different order types as filter value to the two distribution models, but I am still getting "Too many recipients found for message type ORDRSP in the ALE model". Does anybody have an idea on this issue? What am I missing?

Kind regards,

André

[Former Member]

May be this SDN thread will be helpful for you [ALE settings error "Too many recipients found for message type"|;

Regards

Vinod

[Former Member]

Hi André,

I might be wrong, but I suspect that the problem is that you're trying to do something that might not be supported by SAP. To test my theory, please try to use your partner type (i.e. vendor or customer) to define a filter setting instead of your desired order type filter. I suspect that the error message should disappear, as soon as you use the partner number for filtering (so default filter offered by SAP).

Cheers, harald

[Former Member]

Hello Harald,

yes that´s correct. I had already tried this and I think your conclusion that it´s not possible is right. As well the filter just filters segments of the IDOC. So if I want to avoid the sending of an IDoc I have to define a filter for the first segment. I am changing my settings to EDI now this should help.

Kind regards,

André

[Former Member]

So if I want to avoid the sending of an IDoc I have to define a filter for the first segment. I am changing my settings to EDI now this should help.

Well, didn't really think much about your requirement the first time, but if you just want to have different recipients based on order type then it's probably easier to just use EDI and have an output type with an access sequence based on order type (and whatever other criteria you have).

If for some reason you'd still want to use ALE, you could also utilize an implicit enhancement on function module RECIPIENT_GET_FROM_ALE_MODEL and ALE_MODEL_INFO_GET, where you apply the filtering that you want. However, this seems like a pretty awkward solution, so I'd try to use output type with appropriate access sequence and conditions.

[Former Member]

Hello,

we could solve the problem with a change to EDI instead of ALE.

BR, André