Stop sending RON messages back to Supplier after confirmation is sent from supplier

[nevin_philip]

Hi Team,

Needed a small help.We have got a requirement to stop the RON messages triggred after the confirmation messages reach ECC and triggers a message back to SNC and then to supplier hence causing duplication.Can we stop this using some custom programming or through PI level. Kindly check and do let me know

Regards

Nevin

[Former Member]

Hi Nevin,

The RON Messages get trigerred from ECC only when you make changes to ECC PO (Qty / Date / Price) by means of SNC confirmations. This is standard system behaviour to sync ECC & SNC systems.

This will just update the SNC Header Statuses and should not affect your process.

Why do you want to stop it?

Regards,

Bharath

[nevin_philip]

Hi Bharath,

Thanks for your response.We use SNC for the B2B scenarios. So these RON messages after confirmations are going to the suppliers whereby causing confusion within the supplier system causing duplicate PO's. Is there a possibility that this message can be stopped from going from SNC to supplier via PI

Regards

Nevin

[Former Member]

Nevin,

You can stop it at PI (Identify a suitable XML tag in RON which suggests if its a New PO / PO Change) or even in ECC through enhancements (Stop trigerring the message output from ECC when the PO confirmations change the ECC PO).

But the challenge would be in distinguishing an ECC initiated change and SNC initated Change. As you would need any changes made directly on the ECC PO to still flow over to SNC / Supplier system.

Regards,

Bharath

[nevin_philip]

Bharath,

Thanks a lot.Yeah it will be tough to distinguish. Is confirmation mandatory for ASN to happen.We have a request for a vendor to avoid confirmations from SNC.However we were trying a scenario in which the confirmation was put as optional in spro.While doing the ASN directly an error with respect to "notified quantity XX greater than due quantity 00".Do we have to implement some BADI in that case so that due date can be calculated and we can avoid changes at PI level

Nevin

[Former Member]

Hi Nevin,

You may have to due a enhancement in ECC to avoid PO Change trigger once the Supplier Confirms the PO.

Meaning, you can write a requirement routine in  ECC for the 850 Change to check if the change is acutally due to AB line creation and stop such change flow to SNC.

Hope this helps.

Thx

MJ