ERP RSMIPROACT2 for GR - sending duplicate GRs which update Due qty

[Former Member]

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

[Former Member · Accepted solution]

Hi James...

The ASN received should have created an Inbound delivery in ECC for 100 Qty, on that you can change the quantity to 90 and Post GR? in VL32N itself.... and Later you can have 10qty as Open Qty?

Can you try this option?

Regards,

Guru

[Former Member]

Anyone have any inputs for this? Maybe a better way to phrase the question is " How are others handling parital receipt processing on ERP to SNC?

[Former Member]

Hi James,

Its related to validation profiles. There are settings for allowing partial confirmation and according to its update behaviours.

Eventhough, we have had the same problem during implementation of SMI and VMI scenarios. We have implemented few codings for the inbound BADI's in SNC.

As a result, you need to check your validation profiles in a detailed way and then if you can not find any work around then try for the inbound BADIs.

Regards,

Selim

[Former Member]

Hi Selmin,

Thanks for the information - would you happen to know have validation profile that would apply to the partials?

[Former Member]

Hi James,

You can check the below help link for the validation profiles:

Validation Checks for ASNs - Delivery Collaboration - SAP Library

In the validation profiles check the ASN relevant ones like the attached screen shot.

Regards,

Selim

[Former Member]

Hello,

I guess I don't understand quite the connection here (But it could be because its a new system)...

The above describes validations for ASN creations done by the supplier, but the issue is related to sending double receipts to SNC once we receive the ASN ( because of partials or reruning that program multiple times manually etc) - What validation is the connection for this issue, OR is it that there really isn't a connection and is the reason for your BADI implementation and changes to the inbound XML?