Hello,
We are implementing SNC and we are running into an issue regarding rupdating the ASN multiple times when using report RSMIPROACT2 from back end. As an example...
Lets say an ASN is created for 100 qty and send to our ERP system... We see the ASN and receive 90 qty of it (partial) via MIGO_GR..., We run RSMIPROACT2 and based on the SNC configuration of allowing partials, the ASN is updated with 90 received and partial GR status.
We then perform a GR on the remaining 10, and rerun the report - The ASN status is updated as GR complete, but the issue is the RSMIPROACT2 report send again the 90 and also the 10... So the GR received now is 190, and the due list is directly impacted with wrong quantities.
I understand that we would have to change the start time the 2nd time we run this to avoid this specifically, but this isn't practical in that we would be having this program run in the background every 10 minutes, and this could cause issues with missing a GR (because a GR could be done inbetween the first time and last run).
Does anyone have a best practice or solution that will help prevent this from happening? What also is concerning is we make the configuration to close out an ASN after 1 GR, this issue still happens (even with ASN being GR Fully Complete) and will still double update this.
Any help or guidance would be great.
Thanks