Validation Checks for ASNs
The following table lists validation checks that are available for advanced shipping notifications (ASNs):
Technical Name | Short Text | Description |
|---|---|---|
|
| If this validation check is active, you can cancel ASNs that do not have an invoiced quantity. |
|
| If this validation check is active, the system determines the back-end product from the planning product when you enter the planning product on the Web user interface. |
|
| This validation check is relevant for changing ASNs that have the status |
|
| This validation check is relevant for changing ASNs that have the status |
|
| This validation check is relevant for changing ASNs that have the status |
|
| If this validation check is active, SAP SNC first checks if the
|
|
| The ASN header contains a gross weight. The dimension of the unit of measurement is correct. |
|
| If this validation check is active, SAP SNC checks if the ASN item number in the handling unit is valid. |
|
| If this validation check is active, SAP SNC checks if the ASN item contains a gross weight and if the dimension of the unit of measurement for the gross weight is correct. |
|
| If this validation check is active, SAP SNC checks if the ASN item contains a net weight and if the dimension of the unit of measurement for the net weight is correct. |
|
| The item number only exists once in the ASN. |
|
| This check prevents the user from saving an ASN item with a negative quantity. |
|
| If this validation check is active, SAP SNC checks if the ASN item contains a volume and if the dimension of the unit of measurement for the volume is correct. |
|
| If this validation check is active, SAP SNC checks if the ASN contains a kanban ID. If the ASN does not contain a kanban ID, SAP SNC copies the kanban ID from the referenced order document to the ASN. |
|
| Checks that the manufacturer part number (MPN) data in an ASN is valid. That is, the MPN data exists for the characteristics of the ASN in the approved manufacturer parts list. |
|
| If the For more information, see Switching Between Multisourcing and Single Sourcing. |
|
| The ASN header contains a net weight. The dimension of the unit of measurement is correct. |
|
| If this validation check is active, the audit trail does not log changes to the ASN-based in-transit quantity ( |
|
| The ASN number length does not exceed the value specified in the attributes of the number range interval. If no length is specified in the attributes of the number range interval, the ASN number length does not exceed the SAP ERP inbound delivery number length (that is, 10 characters). |
|
| If this validation check is active, the system checks whether the referenced purchase order item does not require manual approval, so that you can create the ASN. |
|
| SAP SNC generates specific ASN alerts using the Post Processing Framework (PPF). If this validation check is inactive, the system performs these actions in the background, but still considers the settings in the PPF action profile. |
|
| If this validation check is active, the system determines the planning product from the back-end product during XML inbound processing. |
|
| The supplier has not changed the product of an item that he or she has already packed in HUs. This check is relevant for changing ASNs manually. |
|
| The supplier has not changed the product of an item for which he or she uses serial numbers. This check is relevant for changing ASNs manually. |
|
| The product of the item is created in SAP SNC. |
|
| The item contains a product. |
|
| The location product of the item is created in SAP SNC. |
|
| This validation check sends the XML message for a published ASN directly in the background. If you deactivate this validation check, SAP SNC uses the Post Processing Framework to send XML messages. |
|
| This validation check is relevant for ASNs with reference to scheduling agreement releases. If this validation check is active, the system writes the changed data of the ASN immediately to the database; it does not wait for an update task to save the changes. |
|
| The sum of the quantity of the ASN item and the due quantity does not exceed the scheduling agreement quantity. |
|
| In SAP ERP, an inbound delivery is canceled, and a new one is created in a short time frame; both inbound deliveries reference the same ASN. Both the cancel and the create operations send out their own IDocs to SAP SNC to cancel an ASN, then to create a new one. These IDocs can arrive in two different orders, one of which results in inconsistencies between SAP SNC and SAP ERP. This validation check handles the problematic case, when the create IDoc precedes the cancel IDoc. It checks the ERP inbound delivery ID of the ASN to be canceled against the ERP inbound delivery ID of the same ASN, which is already stored in the database. SAP SNC processes the cancellation of the ASN only if the ERP inbound delivery IDs are the same. This validation check is relevant for customers using the |
|
| The user has not changed the means of transport. Note: If the user changed the means of transport after the system already executed a scheduling with the previous means of transport for the ASN, the system does not adjust the dates/times to the new means of transport. The user has to delete a date/time in the ASN and, for example, trigger a new scheduling via check. |
|
| If this validation check is active, the system calculates the availability date of the product. |
|
| The system checks if all serial numbers for an ASN item are packed in a handling unit, and all serial numbers found in handling units are maintained in the ASN item. |
|
| When fields for the weights and volumes of an ASN item and the respective units of measurement (UoMs) are empty, the system fills them automatically with data from the product master. |
|
| The system fills the fields for the weights and volumes of an ASN item and the respective units of measurement from the product master, or overwrites values that may have been stored or entered in these fields. |
|
| In the standard system, all successfully validated ASNs that the supplier has sent from his or her system to SAP SNC receive the status |
|
| If this validation check is active, the system calculates the total gross weight, the total net weight, the total volume of the ASN and their respective units of measurement (UoMs) from the referenced products and handling units. The system only saves the result to the database if the user has not entered manual values. |
|
| If this validation check is active, the system calculates the total gross weight, the total net weight, the total volume of the ASN and their respective units of measurement (UoMs) from the referenced products and handling units. The system always saves the result to the database overwriting any values that may have been stored or entered in these fields. |
|
| With the receipt of an XML message of type |
|
| A transportation lane exists between the ship-from location and the customer location. |
|
| The ASN header contains a means of transport and the means of transport exists in SAP SNC. |
|
| The ASN header contains a means of transport and a means of transport type. |
|
| The ASN header contains a volume. The dimension of the unit of measurement is correct. |
|
| The bill-to party in the ASN header and the bill-to party in the purchase order are the same. Note: If the bill-to party in the ASN header is missing, the system copies the bill-to party from the purchase order into the header. |
|
| The country of origin in the ASN item and the country of origin in the purchase order item are the same. |
|
| An ASN accepted in the SAP back-end system with the acceptance status |
|
| The ASN header contains the business partner number of the customer. |
|
| The ASN header contains an ASN number. |
|
| The delivery date/time is not in the past. |
|
| The ASN header contains the location of the goods recipient. If the ASN header does not contain the goods recipient, SAP SNC uses the ship-to location as the goods recipient location. |
|
| The system checks whether the SCAC code ( |
|
| The ASN number does not yet exist. The system performs this check when you manually create an ASN in SAP SNC. |
|
| The item contains an item number. |
|
| The item number does not yet exist. |
|
| The unit of measure of the item is defined in the product master. |
|
| The item contains a unit of measure. |
|
| The item number exists. This check is relevant for changing and deleting an item. |
|
| The ASN header contains a shipping date or a delivery date. At least one of the dates should exist. |
|
| If this validation check is active, inventory is not updated when a goods receipt is posted against an ASN via XML processing. |
|
| If this validation check is active, you must enter a |
|
| In the customer view of ASN processing, you can only set the |
|
| The ASN, identified by ASN number and supplier, exists. This check is relevant for changing and deleting an ASN. |
|
| The shipping date/time is not in the past. |
|
| The ASN item contains the supplier cumulative quantity. |
|
| The combination of ship-from location, customer location, and delivery date does not exist in any other ASN. The check is relevant for creating ASNs. |
|
| The supplier is entered in the location master of the ship-from location. |
|
| The ship-from location exists in SAP SNC. |
|
| The ASN header contains the ship-from location, or there is exactly one ship-from location in SAP SNC for the supplier in the ASN header. |
|
| The total packed quantity of an ASN item and the item quantity are the same. The item is therefore neither underpacked nor overpacked. |
|
| The shipping date is before the delivery date. |
|
| The kanban ID in the ASN item is the same as the kanban ID in the purchase order item. |
|
| There is still no ASN for the kanban purchase order item. This check is relevant for creating an ASN. In standard kanban processing, there can only be one ASN. |
|
| The ASN quantity does not exceed the kanban quantity in the kanban request. |
|
| The quantity of the ASN item does not exceed the open quantity of the kanban purchase order item. You can use this validation check to prevent a supplier creating an ASN item whose quantity is greater than the ordered kanban quantity. |
|
| The quantity of the ASN item does not exceed the open quantity of the kanban purchase order item. You can use this validation check to prevent the supplier creating an ASN item whose quantity is less than the ordered kanban quantity. |
|
| The system performs this validation check when a user publishes a draft ASN. This validation check determines if the kanban for which you want to create the ASN is already set to Full. If the validation check is active and the kanban is already full, you cannot create the ASN. |
|
| The system performs this validation check when a user creates an ASN for a kanban. It determines if an ASN already exists for the kanban. If the validation check is active and an ASN already exists for the kanban, the system creates an error message. |
|
| The original purchase order in the ASN item and the original purchase order in the purchase order item are the same. The check is relevant for third-party order processing. |
|
| The carrier is created in SAP SNC as a business partner. |
|
| The user has not changed the customer. |
|
| The ASN, identified by ASN number and supplier, does not yet exist. This check is relevant for creating an ASN. |
|
| The supplier is created in SAP SNC as a business partner. |
|
| The ASN contains a supplier. |
|
| The user has not changed the supplier. |
|
| The ASN does not have the acceptance status |
|
| This check is relevant for purchase order items. The sum of the quantity of the ASN item and the due quantity of the purchase order (PO) item based on confirmation schedule lines does not exceed the confirmed quantity of the item. SAP SNC considers the overdelivery tolerance for the PO item. |
|
| This check is relevant for replenishment order items and for purchase order items. The sum of the quantity of the ASN item and the due quantity of the purchase order (PO) item or replenishment order (RO) item does not exceed the requested quantity of the item. SAP SNC considers the overdelivery tolerance for the RO item (Supplier Managed Inventory/SMI only) or the PO item. |
|
| This check is relevant for replenishment order items and for purchase order items. The sum of the quantity of the ASN item and the open quantity of the PO item or RO item does not exceed the requested quantity of the purchase order item. SAP SNC considers the overdelivery tolerance for the RO item (SMI only) or the PO item. |
|
| The product in the ASN item is the same as the product in the purchase order item. |
|
| The item contains the number of a valid purchasing document (purchase order or scheduling agreement release). If the document is a purchase order/purchase order item, the system also checks whether ASNs are permitted for the purchase order item. ASNs are only permitted if the purchase order item fulfills the following conditions:
If the document is a scheduling agreement release, the system checks whether a transportation lane exists for the scheduling agreement in SAP SNC. |
|
| The item contains the number of a valid purchasing document (purchase order or scheduling agreement release). If the document is a purchase order/purchase order item, the system also checks whether ASNs are permitted for the purchase order item. ASNs are only permitted if the purchase order item fulfills the following conditions:
In contrast to the |
|
| The ASN item contains a purchasing document reference. |
|
| The goods recipient in the ASN header and the goods recipient in the purchase order are the same. |
|
| This check is relevant for replenishment order items. The sum of the quantity of the ASN item and the due quantity of the RO item does not exceed the requested quantity of the item. SAP SNC considers the overdelivery tolerance for the RO item. |
|
| The number of serial numbers that you have assigned to the ASN item or returns ASN item does not exceed the item quantity. |
|
| The serial number is unique within the ASN or returns ASN item. |
|
| All ASN items are valid. If an ASN item is invalid, the system sets the validation status of the ASN to invalid. |
|
| The ship-from location in the ASN and the ship-from location in the purchase order are the same. |
|
| The supplier in the ASN and the supplier in the purchase order are the same. |
|
| The customer location in the ASN and the customer location in the purchase order are the same. |
|
| The customer in the ASN and the customer in the purchase order are the same. |
|
| The customer is entered in the location master of the customer location |
|
| The customer location is created in SAP SNC. |
|
| The ASN header contains a customer location. |
|
| The third-party order processing in the referenced purchase order is set up in exactly the same way as the third-party order processing in the ASN header. Both indicators are thus set, or both indicators are not set. This check is relevant for third-party order processing. A third-party order processing ASN can only contain third-party order processing purchase items. With this validation check, you can, for example, prevent users from including normal purchase order items in a third-party order processing ASN. |
|
| The ASN header contains a shipping date/time. This check is relevant for TPOP if the location of the goods recipient is not known or if there is no transportation lane between the location of the goods recipient and the ship-from location. In this case, SAP SNC cannot calculate the shipping date/time using scheduling. The supplier must enter the shipping date/time in the ASN header manually. |
|
| The means of transport in the ASN header and the means of transport in the referenced purchase order item or in the referenced scheduling agreement release schedule line are the same. |
|
| A user can change the bill of lading number in the SAP SNC Web user interface (Web UI). This check is relevant if you validate ASNs externally in an SAP back-end system and identify an inbound delivery in the SAP back-end system only via the bill of lading number. (You can make this setting in Customizing for SAP R/3.) In this case, the SAP back-end system does not send a delivery number in the accepted ASN, but sends a bill of lading number to SAP SNC. This bill of lading number must not be changed in the SAP SNC Web UI. With this validation check, you can prevent users from changing the bill of lading number in the Web UI. |
To use the following validation checks, you must activate the business function Supply Network Collaboration 1 (SCM_SNC_GEN_1
):
ASN_SET_TOTALS
ASN_SET_ITEM_WEIGHT_VOLUME
ASN_SPLIT_ITEM_DISPLAY_ONLY