Support for Advance Ship Notice (ASN) in Increff Omni
Â
Overview
Advanced shipping notice (ASN) is a document that provides detailed information about a pending delivery. The purpose of an ASN is to notify when shipping occurs and provide physical characteristics about the shipment so the warehouse can be prepared to accept the delivery.
Generally, ASN contains information on how many of each item are being shipped and the physical characteristics of the shipment such as the shipment’s weight, the number of boxes, and a description of how the shipment units are packaged.
An ASN also tells which mode of transportation is being used for shipping and provides carrier information.
Â
Overall flow
Enabling ASN
ASN creation
ASN updation and cancellation
ASN Approval and rejection
GRN against the ASN
Â
ASN Status Map | Description |
---|---|
VAlidated | Once ASN is created, system does a Listing validation and move ASN to Validated status. |
APPROVED | Supervisor edit validated ASN and mark it as Approved |
MAPPED | ASN is mapped with Gate Entry |
PROCESSING | Receiving for the ASN has started but is not completed. Moves when an ASN is mapped to a gate entry |
COMPLETED | The ASN has been fully received. Moves when gate Entry is closed. |
FAILED | Any ASN that fails listing validation is moved to failed status. |
Â
Enabling ASN Flow
In OMS Partners(Supplier/Customer), the user can set Is ASN Expected field value to let the system know if the ASN creation is mandatory or not.
By Default, this is kept as false.
For Inward Orders, the Value of Is ASN Expected takes priority over Partner priority.
Note: Open PO and Open Returns cannot have ASN created for them.
ASN creation
An ASN can be created either using CIMS UI or using ERP standard APIs.
Please follow the below steps to create an ASN using CIMS.
Go to Create ASN screen
Choose the Client channel pair and Fulfillment location from the dropdown against which ASN is to be created.
Create ASN ScreenAdd the ASN code. For one Inward Order, multiple ASNs cannot be created with the same ASN code.
Secondly, An ASN cannot be created for Inward orders which are created at OMS UI.Enter the Invoice Number and Inward Channel Order ID.
Add the dates for Expected Shipment Arrival and Accepted Shipment Arrival. Expected Shipment Arrival time is to be uploaded/shared by ASN Supplier when the shipment is expected to arrive in the warehouse facility. Accepted Shipment Arrival is the time accepted by the warehouse supervisor for when the shipment is accepted to be received in the warehouse.
Enter the Approver Remarks.
Approver remarks would be required to create so that when the Auto approval functionality is enabled in the future, the Approver Remarks could be added in advance.Download template for ASN line Item CSV Upload. MRP would be required to check and validate the MRP of products received and actually present in masters.
Add the ChannelSKUId, Proposed Quantity, and MRP in CSV file.
Upload the CSV file.
If Inward Order SKU Line item doesn't match with ASN Line items then error is thrown to ERP system and ASN will not be created. Eg, If ASN line item is not present in Inward Order, ASN will not be created.
If Inward order is in Failed status, the ASN will also move to Failed status.
ASN Approval
ASN Approval is mandatory to be done in spite of the ASN creation source (ERP or CIMS Upload).
ASN first moves to Validated status means the ASN is validated by checking the Channel Listings and Order line items in inward orders.
Steps to be followed
Go to Approve ASN screen
Choose Client Channel Pair, Fulfillment Location. Enter Channel Order Id and ASN Code as well to search which needs to be approved.
Approve ASN ScreenAccepted Shipment Arrival Time under ASN Details is required to be added at the time of Approval of ASN.
Click on Edit Approved Quantity.
Download the CSV template.
Add the Channel SKU, Proposed Quantity, Approved Quantity, and Approval Remarks. ApprovedQty in CSV at the time of approval can be edited multiple times by the user, thus the value of ApprovedQty is absolute when given in CSV.
ApprovedQty can be greater than ProposedQty as well, there is no validation with a checkpoint of Inward Order line item qtyAfter ASN is APPROVED, ASN Approval Postings will be sent to ERP system(if ERP is integrated).
Failed ASN would be required to be canceled in system to complete the Inward Order. post that the failed ASN moves to Failed status.
New Updates
Auto Approval of ASN
With latest release (Sprint version 73) of Increff Omni system, we have now introduced the capability of implementing auto-approval on ASNs during the ASN creation process done by ERP systems with help of Create ASN API.
ASN wil be moved to APPROVED state in case all validations are being passes , else it will be moved to FAILED state in CIMS module.
For more details about ASN failure you can refer to ASN creation section of this document.
ASN Updation and Cancellation
In Manage ASN Screen, user can do ASN Updation and ASN Cancellation from UI.
User can update ASN Code, Invoice Number and ASN Line items from Manage ASN Screen.
ASN Code and Invoice Number can be updated before the ASN is Approved as part of ASN Approval process. User can click on the edit action button against any ASN created in Manage ASN Screen
ASN Line Item Updation can also be done by from Manage ASN screen by use of Edit button present in Line Items section to download the CSV file.
There are two types of CSV files available that can be uploaded in User Interface.Item CSV Upload: User can use this CSV file to update the existing values of channelSkuId, proposedQty, mrp fields against every line item for the ASN .
Blank Template CSV: User can use this CSV file to specify new values of channelSkuId, proposedQty, mrp in the blank fields against every line item for the ASN .
Note:
Once the Line items are updated ASN will again move to NEW Status.
Validation will happen again once the line items are updated in an ASN
ASN Cancellation
ASN cancellation can be done at the Manage ASN screen for all FAILED ASNs.
Multiple FAILED ASNs can also be cancelled at one time by selecting them through Checkboxes.
After selecting FAILED ASNs which needs to be cancelled the User can click on Cancel Selected ASN button present on bottom right side of the User Interface.
Â
Checking Approved ASNs
ASN Details are present in Inward Order Details
Supervisor remarks can also be updated from OMS
Creating Gate entries against ASN in WMS
Please follow the below steps to map the ASN to gate entry.
During Gate Entry Creation, Inward PO is searched and selected as usual.
Once Inward PO is selected, If the configuration of ASN required is set as True for the Supplier then the system makes it mandatory to select ASN to be mapped accordingly.
For any Inward PO with this property set as False for the Supplier, ASN mapping is optional for user.All the ASN for the inward order which will be in APPROVED status are displayed to be selected and mapped here.
Only Unmapped ASNs will be displayed in the Gate Entry creation screenSelect ASN to Map in WMS Gate EntryThe user can capture other details related to Gate Entry as usual and create the gate entry.
When Gate Entry is closed, ASN Details will also go in Gate Entry and GRN Postings to ERP System.
API Details
New APIs
New APIs | Description | Reference Links |
---|---|---|
ASN Approval Posting API | This API can be used for sending notification to ERP system for ASN Approval | |
Create ASN Inward Order API | This API can be used to create ASN for an Inward Order. | |
Update ASN Inward Order API | This API can be used to update an ASN created for a particular order. |
Existing APIs Enhancements
Exisiting API | Description | Reference Links |
---|---|---|
Modifications in GRN and Gate Entry Close Postings to ERP | There are some additional fields added in GRN Postings APIs and Real Time GRN Noitifications APIs New Fields: GRN Posting API (Order Level)
GRN Posting API (Gate Entry Level)
Real Time GRN Notifications API (Order)
Real Time GRN Notifications API (Gate Entry Level)
| GRN Posting API (Order Level)(Beta) GRN Posting API (Gate Entry Level)(Beta) |