Inbound ASN Automation Best Practices and Limitations

Before using the Inbound ASN Automation SuiteApp, be aware of the current limitations and best practices.

Best Practices

Make sure you keep the following in mind before using the Inbound ASN Automation SuiteApp:

To ensure that the ASN is uploaded successfully, you must note the following:
- Do not edit or delete header names in JSON and CSV file.
- Enter values in the following required fields:
  - Advance Ship Notice (ASN) Document
  - Vendor ID or Name
  - Purchase Order Number
  - Item Number
  - Shipment Qty. This field is required for item lines only.
To add only landed cost details:
- Keep the Shipment Qty field blank.
- If the landed cost applies to all items, set the Item Number to All.
- If the landed cost applies to a single item, enter the item name in the Item Number field. For multiple items, enter the items separated by semi colon.

Look out for the following limitations before using the Inbound ASN Automation SuiteApp:

One ASN can contain a maximum of 700 line items.
Inbound shipment record can be created with a maximum of 1,000 line items.
To handle purchase orders with item overage, the SuiteApp can receive:
- Item overage from 80 purchase orders only if you have set Create New PO preference.
- Item overage from 160 purchase orders only if you have set Edit PO preference.
The SuiteApp supports only one Unit of Measure for an item in a purchase order. If an item has multiple units of measure in a purchase order, the SuiteApp cannot derive the unit of measure for that item in the ASN. So, the SuiteApp won't create an inbound shipment record for the ASN and will set the ASN status to Error.

To create an inbound shipment record, you can remove the items with multiple units of measure from the ASN to change the ASN status to Success. Then, you can manually add those items to an existing inbound shipment record or create a new one.