ASN Data
An advanced shipping notification (ASN) contains, for example, the delivery date and the items with the quantities being delivered. SAP Supply Network Collaboration (SAP SNC) displays the ASN data on the user interfaces for ASN processing. The following tables provide an overview of the data in the ASN details:
Field |
Description |
|---|---|
|
Alphanumerical character string that uniquely characterizes the ASN in SAP SNC. Note that SAP SNC allows an ASN number to be 35 characters long. However, an SAP back-end system can only process 16 characters. You must restrict the length of ASN numbers in SAP SNC to 16 characters in the following cases:
|
|
Number of the ASN in the customer's back-end system. This field is relevant for the |
|
Time at which the delivery is to arrive at the ship-to location. If the ship-to location is the same as the customer location, or if the ship-to location is not a location in SAP SNC, SAP SNC displays the delivery date in the time zone of the customer location. |
|
Location of the supplier sending the delivery. |
|
Location that ordered the products. |
|
Location that receives the delivery. |
|
Date on which the supplier created the ASN. An entry in this field is optional. |
|
Date and time at which the delivery leaves the ship-from location. |
Field |
Description |
|---|---|
|
Processing status of the ASN (see ASN Status). |
|
Status of the ASN header. This status indicates whether the ASN header is valid or invalid according to validation. |
|
This field is only relevant for the |
|
Indicator for an ASN in third-party order processing. In third-party order processing, the delivery does not go to the customer, but directly to the customer's customer. |
|
Status of the inbound delivery in warehouse processing. This field is only relevant for the
|
|
System in which the ASN was created. This field is only relevant for the
|
|
Indicator for an ASN that belongs to a delivery that SAP EWM has split. ASNs that belong to a split delivery have the same ASN number but different internal ASN numbers. |
Field |
Description |
|---|---|
|
Key used by a third party to group ASNs. |
|
Unique ID of the freight invoice. A freight invoice is the invoice for the certified transportation of goods from a supplier to the goods recipient, as specified in the bill of lading. |
|
A service agent who is exclusively responsible for transporting goods. On the Web user interface (Web UI), you can see the carrier number as it has been maintained in the business partner transaction. |
|
Standard Carrier Alpha Code for the carrier. The Standard Carrier Alpha Code is the recognized transportation company identification code used in the American National Standards Institute (ANSI) Accredited Standards Committee (ASC) X12 and United Nations EDIFACT approved electronic data interchange (EDI) transaction sets. |
|
The system uses the transportation duration of the means of transport specified here for scheduling. |
|
The official rules of the International Chamber of Commerce (ICC) regarding how to define trade terms. The |
|
Location related to an Incoterm, that is, the location where goods are transferred. The |
|
Weight and volume data. You enter the data manually. SAP SNC does not calculate the data from handling unit (HU) data. You can only transfer this ASN header data to an SAP back-end system if you use Discrete Industries and Mill Products (DIMP). A non-DIMP system determines the data from the item data. |
Field |
Description |
|---|---|
|
|
|
|
|
Number that identifies the purchasing document for which the supplier has created the ASN, for example, a purchase order. |
|
Number of the original purchase order. This field is only relevant to third-party order processing. |
|
Item number in the original purchase order. |
|
Weight data for the item. You enter the data manually. SAP SNC does not calculate the data from HU data. |
|
A batch of a product that is batch-managed by the customer. The customer creates the batches for a product in the customer back-end system as part of purchase order data. The purchase order data from the customer back-end system, including the batch information, is transferred to SAP SNC and copied to the purchase order data in SAP SNC. If the purchase
order contains a reference to an ASN, the batch information is also written into the
Supplier batch numbers are not displayed on the End of the note. |
NoteUnloading Point
The unloading point is only relevant in a scenario with an SAP back-end system if you use a DIMP system or, for the Service Parts Management
scenario, SAP ERP with activated service parts management.
Note: The number of the unloading point has 20 characters in SAP SNC. If the number of the unloading point in an inbound message is longer than 20 characters, the system only uses the first 20 characters when mapping to the XML message.
Time Specifications
In SAP SNC, time specifications are shown referring to the following time zones:
Time data that refers to a location is shown in the time zone of the relevant location. Example: the shipping date/time in an ASN is displayed in the time zone of the ship-from location. The delivery date/time is displayed in the time zone of the customer location or of the ship-to location.
Time data that does not refer directly to a location or to a business partner is displayed in the time zone of the user that is logged on to the system. This includes, for example, the time at which the ASN was last updated.
Creation and Change Time
In ASNs and purchase orders, there is a time of the last change and a creation time on the SAP SNC Web user interface (Web UI) at header level and in the administration details, as follows:
The creation and change times at header level are transferred to SAP SNC with the XML message. The dates show when the document was created or last changed in the back-end system.
The creation and change times in the administration details show when the document was created or saved in order document management (ODM).