Quantcast
Channel: SCN: Message List - ABAP Connectivity
Viewing all articles
Browse latest Browse all 3125

Re: Too many recipients found for message type SHPMNT in the ALE model

$
0
0

Hi Jack

We’re using transmission medium ALE and not EDI. My understanding is that EDI does not work for partner type LS, but do work for KU and LI (but I’m uninformed on this subject).

I’ve changed output control in tcode NACE to use EDI with RSNASTED / EDI_PROCESSING.

We are now faced with a different error during delivery output:

 

Maintain outgoing EDI-connection data for partner CMESWBDO

Message no. VN032

Diagnosis

The system could not locate the EDI partner agreements (outbound) for

partner CMESWBDO.

System Response

You cannot use transmission medium 'EDI' with this partner.

Procedure

Maintain the EDI partner agreements for partner CMESWBDO. Make sure to

create entries for output control as well as for outbound parameters.

 

Partner CMESWBDO is defined in WE20 as type LS and all other settings (e.g. message control) are correct. Not sure if EDI requires additional settings when compared to ALE.

Also, when using EDI, the Delivery output in VL32N does not default. We have to manually add the Output type (and we have maintained the condition records in NACE).

 

The only other solution is to create a new Z message type for each Logical system and link relevant Basic types to them. But this seems a bit extreme as I’m sure there must me a standard SAP solution for our required Distribution model.

 

Regards

Werner


Viewing all articles
Browse latest Browse all 3125

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>