Overview

Customers may experience issues with Advanced Shipping Notices (ASNs) not being associated with the correct Purchase Orders (POs) and Goods Receipt Notes (GRNs) not reflecting in OneSCM. This problem typically arises when the ASNs for a list of POs need to be resent, and the support team encounters difficulty in identifying the ASNs mapped to the given POs. Additionally, no entries for the GRNs on the listed POs may be found, particularly for older POs that had to get ASNs re-pushed.

Solution

To resolve the issue of ASNs not being associated with the correct POs, follow these steps:

1. Provide the list of ASNs corresponding to the given POs. This information is usually found in a specific column in your data (in this case, column D or G).
2. Once this information is provided, the support team can reprocess the ASNs.

For the issue of GRNs not reflecting in OneSCM, follow these steps:

1. Verify on your ERP side if the GRN was sent successfully.
2. If the GRNs are not showing as receipted, especially for older POs that had to get ASNs re-pushed, resend the GRNs from your ERP side.

Summary

By providing the correct ASNs for the POs and verifying and resending the GRNs from the ERP side, customers can resolve issues of missing ASNs and GRNs in OneSCM.

FAQ

1. What should I do if the ASNs are not associated with the correct POs?
   Provide the list of ASNs corresponding to the given POs to the support team for reprocessing.
2. What should I do if the GRNs are not reflecting in OneSCM?
   Verify on your ERP side if the GRN was sent successfully. If not, resend the GRNs from your ERP side.
3. What should I do if the GRNs are not showing as receipted for older POs?
   Resend the GRNs from your ERP side, especially for older POs that had to get ASNs re-pushed.