Advance Shipping Notice (ASN) Document

This topic describes the Advance Shipping Notice (ASN) service and document and the associated business logic in Microsoft Dynamics AX.

Business Purpose

Enables external systems to receive information about shipments. The ASN document is a delivery confirmation and is used to notify a customer about an expected delivery. The ASN is typically generated based on information that is available when a shipment has left the warehouse, and it can be triggered when you post a packing slip in Microsoft Dynamics AX.

For example, when an order is ready to be picked, a picking list is created. Warehouse employees pick items from the inventory and prepare them for shipment. When the order has been shipped, this triggers the order status to be updated which in turn triggers the ASN to be sent from Microsoft Dynamics AX to the customer.

Document Direction

  • Outbound

Service Operations

The following service operations are exposed by the document service:

  • find

  • findKeys

  • read

The following objects are associated with the ASN service.

Object

Description

Service class

InventASNService Class

External service name

ASNService

Axd <Document> class

AxdASN Class

Ax <Table> classes

AxCustPackingSlipJour Class

AxCustPackingSlipTrans Class

AxWMSBillOfLading Class

AxWMSBillOfLadingOrder Class

AxWMSBillOfLadingCarrier Class

AxDocuRef Class

AxFormLetterRemarks Class

AxInventDim Class

AxInventReportDimHistory Class

AxWMSPallet Class

AxInventSerial Class

Query

AxdASN

Document Processing Rules

Outbound

The ASN is sent automatically from the SalesEditLines form and manually from the CustPackingSlipJournal and WMSShipment forms.

Inbound

N/A

Restrictions

An ASN can be sent from Microsoft Dynamics AX multiple times.

Document Data Sources

Table Relationships

The AxdASN document class is based on the AxdASN query. The parent table of this query is the CustPackingSlipJour table. The parent table is related to tables CustPackingSlipTrans, WMSBillOfLading, WMSBillOfLadingCarrier, and WMSBillOfLadingOrder.

The DocuRefJour table is associated with both the CustPackingSlipJour parent table and the CustPackingSlipTrans table. The FormLetterRemarks table is associated only with the parent table CustPackingSlipJour. The WMSPallet and InventSerial tables are related to the InventDim table which is related to the CustPackingSlipTrans table through the InventReportDimHistory table.

Note

The InventReportDimHistory table is used for transactional references. For example, when you resend a copy of the document, it must be identical to the original. The InventReportDimHistory table is used in the AxdASN query but it is not used in the AxdASN document.


Note Field Handling

The outbound ASN document can contain form notes and remarks that must be processed when the ASN document is created. Tables that contain form notes include the following:

  • DocuRef

  • FormLetterRemarks

Form notes in the ASN document are created in the DocuRef table using the built-in business logic in Microsoft Dynamics AX.

When calling the read, find, and findKeys service operations on the InventASNService, only notes of the type "External" can be added from the DocuRef table.

The following relations between the DocuRef table and other tables must be respected when you integrate ASN documents.

Adding Notes to the ASN Header

DocuRef.RefRecId = CustPackingSlipJour.RecId

DocuRef.RefTableId = CustPackingSlipJour.TableId

DocuRef.RefCompanyId = CustPackingSlipJour.DataAreaId

DocuRef.TypeId = CustFormLetterDocuments.DocuTypePackingSlip

DocuRef.Restriction = "External"

CustFormLetterDocuments.DocuOnSalesOrder = "Header" or "All"

Adding Notes to the ASN Line

DocuRef.RefRecId = CustPackingSlipTrans.RecId

DocuRef.RefTableId = CustPackingSlipTrans.TableId

DocuRef.RefCompanyId = CustPackingSlipTrans.DataAreaId

DocuRef.TypeId = CustFormLetterDocuments.DocuTypePackingSlip

DocuRef.Restriction = "External"

CustFormLetterDocuments.DocuOnSalesOrder = "Lines" or "All"

Required Fields

The mandatory fields for sending ASN documents are identical to the mandatory fields for receiving packing slip documents. Mandatory fields must follow Microsoft Dynamics AX business logic requirements for posting a valid packing slip.

Excluded Fields

Field Defaults

Constraints

Entity Key

Parameter Settings

Security Settings

The security key is found on the Permissions form under Accounts receivable > Services > InventASNService. The key name is InventASNService.

The record-level security (RLS) settings required for sending the ASN document electronically are the same as the RLS settings required for printing the document. By default, RLS is bypassed when you create and send the ASN document electronically.

Deviations from Standard Business Logic

Posting and Sending an ASN Electronically

Sending an ASN is linked to the posting of the packing slip. It is possible to send an ASN multiple times, in two different ways, depending on whether the Warehouse Management System (WMS) module is installed.

Posting Without WMS

The ASN will be sent the first time that you post the sales order packing slip.

To send an ASN manually after a packing slip has been posted, open Accounts receivable > Inquiries > Journals > Packing slip. Click Send ASN electronically.

Posting With WMS

The ASN will be sent the first time that you post the packing slip on the Shipment form by going to Inventory Management > Common Forms > Shipments. Click Functions and select Packing slip.

To send an ASN manually after a packing slip has been posted, open Inventory Management > Common Forms > Shipments. Click Functions and click Send ASN.

Additional Information

Trading Partner Identification

Trading partner identification for the ASN document is determined by the following values:

  • Partner Type - The value of the partner type field is set by the AxdASN class to "Customer."

  • Partner ID - The partner ID is derived from the CustPackingSlipJour.OrderAccount field.

RFID

It is possible to enclose the RFID Tag ID for pallets and for items in the ASN document.

See Also

Standard Axd Documents