Skip to Content
0
Former Member
Jan 12, 2009 at 11:26 AM

MM - SUS: problems with ASN created from scheduling agreement releases

107 Views

Hi to All,

we have a MM - SUS scenario: the buyer creates scheduling agreement on ECC6 and send scheduling agreement releases (SAR) to SUS. the Supplier displays SAR and sends ASN from SUS to MM. The communication between ECC and SUS is managed by XI (standard scenario and interfaces). We have a problem on ECC6 when we receive from SUS the idoc containing the ASN data: the idoc is not registered (error message: Function module not allowed: BORES_IDOC_INPUT_DESADV1).

For the ASN process we set following configurations on ECC6 (trx WE20):

Inbound Idoc

message type: DESADV

type: delvry01

process code: DELS (=> that is related to FM BORES_IDOC_INPUT_DESADV1)

We didn't find any OSS note regarding this problem: some suggestion?

Thanks in advance.

Francesca Martinelli

Edited by: Francesca Martinelli on Jan 12, 2009 12:29 PM

Edited by: Francesca Martinelli on Jan 12, 2009 12:31 PM