Creating ASNs Manually in SAP SNC This process describes how you, as supplier, can manually create an advanced shipping notification (ASN) in ASN processing in SAP Supply Network Collaboration (SAP SNC) and send it to the customer. Note the following constraints:
You cannot enter any freight costs.
You can either include third-party order processing items only or normal purchase order items only in an ASN. A combination of both is not possible.
The following prerequisites apply to the creation of ASNs:
You have authorization to create ASNs.
In the case of scheduling agreement releases and purchase orders, confirmation control enables the creation of ASNs.
The properties and status of the document and the document item enable the creation of ASNs. For more information, see Creating ASNs for a Purchase Order Item and Functions in Release Processing .
The ASN-based due quantity of the document schedule is greater than zero. If the due quantity is zero, you cannot create ASNs.
Call ASN processing. To do so, you can select one of various options .
Enter the required data on the
ASN Header
tab page. Note the following:
If you create an ASN for a planned receipt or for an order document, the system automatically transfers the data into the ASN. This data includes the delivery date, the ship-from location, the customer location, and the ship-to location.
If you enter either only the delivery date or only the shipping date, SAP SNC uses scheduling to automatically calculate the other date in each case when you save the ASN. You can also enter both dates. In this case, SAP SNC does not perform scheduling.
You only have to enter the ASN number if system administration has set external number assignment for ASNs. In internal number assignment, SAP SNC generates an ASN number automatically.
Enter the optional data on the remaining tab pages if required. This data is not mandatory but is important if you want shipping processing to run smoothly.
Create the ASN items. To create an ASN item, you choose the
Add Item
function in the
ASN Items
screen area. In addition to the product and the quantity, enter, for each item, the number and item of the customer’s order document to which the ASN item refers. This means the customer can link the ASN with the order document and the item. This is important for posting goods receipts. You can use
rounding
to round the item quantity to a whole-numbered multiple of the rounding value set for the location product. You can delete an item again, if required, by choosing
Delete Item
. If required, you enter additional, optional item data such as the batch number or dangerous goods data.
If required, choose
Check
to perform an SAP SNC-internal
validation
. In the validation, SAP SNC checks whether the ASN data at header level and at item level is complete and correct. Fill in the missing data or correct the incorrect data, as required. You can save an ASN that is not correct. In the standard system, incorrect ASN data or an incorrect ASN header acquire the validation status
Invalid
in accordance with the standard settings in Customizing for
Validation
.
If you save the data you have entered, but want to continue processing the ASN (possibly at a later time), save the ASN as a
draft
. The ASN acquires the
Draft
process status. SAP SNC automatically performs an internal validation.
Pack the ASN items manually or automatically, as required; in other words, create handling units and print labels and the delivery note.
Note
Packing is not relevant for service parts management.
If you want to send the ASN to the customer,
publish
the ASN. SAP SNC also performs a validation automatically in this case. If the ASN does not show any errors, SAP SNC publishes the ASN; in other words, the ASN acquires the process status
Published
and SAP SNC sends the ASN to the customer. If the ASN contains errors, you cannot publish it in the standard system. This is specified in Customizing for
Validation
. The relevant subobjects (ASN items or ASN header) acquire the validation status
Invalid
and the ASN retains the process status
Draft
. To be able to publish the ASN, you must first correct the incorrect data.
You have sent the ASN to the customer.
In the Service Parts Management scenario, SAP SNC sends the ASN for external validation to the customer backend system (SAP ERP with activated Service Parts Management), which then validates the ASN. In SAP SNC you must wait on the validation result and, if required, then postprocess the ASN. During the waiting time, the ASN has the acceptance status
Pending
and cannot be changed. For more information, see
Processing ASNs in Service Parts Management
and
External Validation
.