Validation Checks for Purchase Orders
The following table lists the validation checks that are available for purchase orders (POs):
Technical Name | Short Text | Description |
|---|---|---|
|
| The system performs this validation check when a kanban request is received by SAP SNC. It determines if the kanban request has the same or a higher quantity than the kanban container maintained in the control cycle. If the validation check is active and the quantity in the kanban request is lower than the quantity in the kanban container, the system creates a warning message and continues to process the kanban request. |
|
| This check is relevant for the approval process. If this check is active, only those purchase order items that have the |
|
| If an ASN is published, SAP SNC sets the status of all PO items to |
|
| If an ASN is published, SAP SNC sets the status of the PO item that references the ASN to |
|
| The bill-to party exists in SAP SNC as a business partner. |
|
| The customer is entered in a location in the location master in SAP SNC. |
|
| The purchase order contains a customer. |
|
| The customer exists in SAP SNC as a business partner. |
|
| The schedule line of the subcontract order contains a component requirement for a subcontracting component. A product master exists for the subcontracting component in SAP SNC. |
|
| The subcontracting component in the purchase order (PO) item contains a product. |
|
| The schedule line of the subcontract order contains a component requirement for a subcontracting component. The component requirement contains the quantity of the subcontracting component. |
|
| The unit of measure for a component exists in the product master data in SAP SNC. |
|
| The schedule line of the subcontracting order contains a component requirement for the subcontracting component. The component requirement contains the unit of measure of the subcontracting component. |
|
| The system copies the confirmed price to the price field in a purchase order. |
|
| The schedule line of the purchase order item contains manufacturer part number data. This check is relevant, for example, when the supplier saves or publishes a purchase order confirmation on the Web user interface or when SAP SNC receives a purchase order confirmation from the supplier back-end system. |
|
| If this validation check is active, SAP SNC sets the confirmation status of a purchase order (PO) item to
|
|
| After having accepted a purchase order confirmation schedule line manually, the customer has also updated the request schedule line by choosing the |
|
| All confirmation-relevant purchase order items have been confirmed. |
|
| If this validation check is active, SAP SNC deletes the confirmations schedule lines of a purchase order item if the customer has performed a change that requires confirmation by the supplier. Changes that trigger deletion include the following: Quantity changes and the changes listed in the description for validation check |
|
| The purchase order item contains at least one confirmation schedule line of schedule line type |
|
| If this validation check is active, SAP SNC assigns a contract to the purchase order item if the purchase order item does not reference a contract. Moreover, the system copies the order unit, the unit conversion factors and the tolerances from the contract or info record (if no contract exists) into the PO item. |
|
| This validation check is relevant for the approval process. If the validation check is active, SAP SNC adopts the accepted confirmation schedule lines as request schedule lines in the purchase order item. |
|
| Like the validation check |
|
| The same currency is assigned to all items within a purchase order. |
|
| The delivery date is not in the past. |
|
| The schedule line contains the delivery date/time. |
|
| The ship-from location of the item contains the same supplier as the purchase order header. |
|
| If the purchase order item does not contain a ship-from location, SAP SNC assigns a ship-from location to the purchase order item as follows:
|
|
| The ship-from location exists in SAP SNC. |
|
| The purchase order item contains a ship-from location. |
|
| If the purchase order item does not contain ship-to location data (ID and address), SAP SNC assigns a ship-to location to the purchase order item as follows:
|
|
| The ship-to location exists in SAP SNC. |
|
| If the purchase order item does not contain a goods recipient, but does contain a ship-to location ID, SAP SNC assigns the item the business partner entered in the ship-to location as the goods recipient. |
|
| The goods recipient exists in SAP SNC as a business partner. |
|
| If this validation check is active, SAP SNC sets the invoice creation type for the PO item depending on the
For invoice creation, you activate either this validation check or the |
|
| This validation check assigns invoice-relevant data to the purchase order item. SAP SNC uses the data from the contract or from the purchasing info record that is assigned to the purchase order item. |
|
| If this validation check is active, the invoice creation type is |
|
| The purchase order item contains an item number. If the purchase order item does not contain an item number, SAP SNC assigns a number to the purchase order item. |
|
| The purchase order contains at least one item. |
|
| The confirmed quantity lies within the overdelivery tolerance. |
|
| The confirmed quantity lies within the overdelivery tolerance. If the value of the overdelivery tolerance is zero, the check tolerates all overdeliveries. This check is relevant if you do not use delivery tolerances and the supplier is allowed to create as many confirmation schedule lines with as many confirmation quantities as desired. |
|
| The confirmed quantity lies within the underdelivery tolerance. |
|
| The confirmed quantity lies within the underdelivery tolerance. If the value of the underdelivery tolerance is zero, the check tolerates all underdelivereries. This check is relevant if you do not use delivery tolerances and the supplier is allowed to create as many confirmation schedule lines with as many confirmation quantities as desired. |
|
| This validation check copies the schedule line quantity of a purchase order in SAP SNC to the purchase order SL if a Kanban item is canceled and the quantity transferred in the XML message is zero. |
|
| This validation check is relevant when the customer sends an updated kanban request to SAP SNC and the kanban request item does not contain the Kanban ID. If the validation check is active, SAP SNC sets the Kanban ID to the Kanban ID that the customer transmitted in the predecessor kanban request. |
|
| The kanban request contains only one item. |
|
| The kanban request item contains only one schedule line. |
|
| The kanban ID is not used in another kanban request. |
|
| A transportation lane exists in SAP SNC between the ship-from location and the customer location. |
|
| The product exists in SAP SNC in the ship-from location. |
|
| The product exists in SAP SNC in the customer location. |
|
| This validation check checks whether the MPN data in a purchase order is valid. That is, the MPN data exists for the characteristics of the purchase order in the approved manufacturer parts list. This check is carried out for a purchase order confirmation, only when the confirmed MPN data and the requested MPN data differ. |
|
| If this validation check is active, SAP SNC creates alerts when the customer sends a purchase order with a new or a changed PO item from his or her back-end system to SAP SNC. For new PO items, the alert type is |
|
| If this validation check is active, SAP SNC does not generate an alert (of type |
|
| If this validation check is active, the audit trail does not log changes to the purchase order-based all orders ( |
|
| If the supplier in SAP SNC creates an ASN for a purchase order item, SAP SNC creates an ASN-confirmed schedule line for the PO item. This validation check updates the open quantity of the request schedule lines of a PO item at the receipt of a goods receipt (GR) message using the GR quantity of the ASN-confirmed schedule line referring to the ASN. The validation check first calculates the open quantity of the request schedule line with the earliest delivery date as follows: Open quantity of request schedule line = requested quantity of request schedule line minus GR quantity of ASN-confirmed schedule line. If the requested quantity of the earliest request schedule line is less than the GR quantity of the ASN-confirmed schedule line, SAP SNC can reduce the open quantity of the request schedule line to zero. SAP SNC uses the remaining GR quantity to successively reduce the open quantities of later request schedule lines. The check also compares the total open quantity of a PO item with the total requested quantity. If the open quantity lies within the underdelivery tolerance, SAP SNC sets the item status to |
|
| If the supplier in SAP SNC creates an ASN for a purchase order item, SAP SNC creates an ASN-confirmed schedule line for the PO item. This validation check updates the open quantity of the request schedule lines of a PO item when the ASN is published based on the planned delivery quantity of the ASN-confirmed schedule line. The validation check first calculates the open quantity of the request schedule line with the earliest delivery date as follows: Open quantity of request schedule line = requested quantity of request schedule line minus planned delivery quantity of the ASN-confirmed schedule line. If the requested quantity of the earliest request schedule line is less than the planned delivery quantity of the ASN-confirmed schedule line, SAP SNC can reduce the open quantity of the request schedule line to zero. SAP SNC uses the remaining delivery quantity to successively reduce the open quantities of later request schedule lines. The check also compares the total open quantity of a PO item with the total requested quantity. If the open quantity lies within the underdelivery tolerance, SAP SNC sets the item status to |
|
| The validation check calculates the open quantity of the request schedule line as follows: Open quantity = requested quantity minus goods receipt quantity from request schedule line For an SAP customer back-end system, note that although the back-end system does update the goods receipt (GR) quantity of the request schedule line in the purchase order at goods receipt, it does not send an updated PO to SAP SNC at goods receipt. The goods receipt information only goes to SAP SNC with other information, for example if the customer changes the purchase order manually later. The check also compares the total open quantity of an item with the total requested quantity. If the open quantity lies within the underdelivery tolerance, SAP SNC sets the item status to |
|
| SAP SNC was able to assign a number from a number range interval to the purchase order with internal number assignment. |
|
| SAP SNC generates specific purchase order alerts and connects to supplier delivery performance rating using the Post Processing Framework (PPF). Note: If this validation check is inactive, the system performs these actions in the background, but still considers the settings in the PPF action profile. |
|
| This validation check assigns price data to the purchase order item (not to consignment items). SAP SNC uses the price data from the contract that is assigned to the purchase order item. |
|
| This validation check calls deviation analysis for the confirmed price in a purchase order item. |
|
| The product exists in SAP SNC. |
|
| The purchase order item contains a product. |
|
| If this check is active, SAP SNC sends the |
|
| This check is relevant for the approval process. If this check is active, only those purchase order items whose schedule lines have changed will be transferred using |
|
| This validation check sends the XML message for a purchase order published by the customer or a purchase order confirmation published by the supplier directly in the background. If you deactivate this validation check, SAP SNC uses the Post Processing Framework to send XML messages. |
|
| SAP SNC sends and receives purchase order XML messages that are compatible with IDocs. If this validation check is active, the system uses XML messages that are compatible only with a back-end system as of enhancement package 4 for SAP ERP 6.0. |
|
| If batch data is missing from a |
|
| If manufacturer part number (MPN) data is missing from a |
|
| The request schedule line contains a schedule line number. |
|
| The purchase order item contains at least one request schedule line. |
|
| The request schedule line or |
|
| The quantity in a purchase order schedule line is greater than or equal to zero. |
|
| The unit of measure of the item exists in the product master in SNC. |
|
| The schedule line contains a unit of measure. |
|
| The request schedule line or the |
|
| This validation check is relevant for scheduling the delivery date of PO schedule lines that fulfill the following conditions:
If the validation check is active, SAP SNC moves the delivery date to the next working day. |
|
| The seller exists in SAP SNC as a business partner |
|
| The shipping date is not later than the delivery date. |
|
| The shipping date is not in the past. |
|
| The schedule line contains a shipping date/time. |
|
| SAP SNC was able to assign a sales order number from a number range interval to the replenishment order with internal number assignment. |
|
| The purchase order refers to exactly one sales order. All purchase order items refer to different sales order items. (A particular combination of sales order number and sales order items can only exist in exactly one purchase order item.) |
|
| This validation check enters the sales order number that you specified for a purchase order item on the Web UI in all other purchase order items of the purchase order when you save or check the purchase order. |
|
| There can only be one purchase order per sales order. |
|
| The customer location contains a customer. |
|
| The customer location exists in SAP SNC. |
|
| The purchase order item contains a customer location. |
|
| This validation check is relevant if the customer uses an SAP back-end system. The |
|
| If the purchase order item does not contain a means of transport, SAP SNC assigns a means of transport to the purchase order item as follows:
|
|
| The means of transport that is assigned to the purchase order item is assigned to a transportation lane in SAP SNC. The means of transport is also valid at the earliest request delivery date/time. (You can assign a validity period to a means of transport in the transportation lane). |
|
| If this validation check is active, the customer is able to change the purchase order item, that has been rejected by the supplier, in their SAP ERP system. |
|
| The supplier is entered in a location in the location master in SAP SNC. |
|
| Purchase order contains a supplier. |
|
| The supplier exists in SAP SNC as a business partner. |
|
| If a purchase order is created or changed in SAP SNC based on an XML message, a |
|
| This validation check is relevant for purchase order confirmations (
|
|
| This validation check is relevant for confirmations ( |
|
| The number of PO items transmitted via |
|
| This validation check is relevant for confirmations ( |
|
| If the price unit or price unit of measure in the purchase order confirmation received from a supplier back-end system differs from that of the purchase order in SAP SNC, the system converts the confirmed price in the confirmation to so that it uses the same unit or unit of measure as the purchase order item in SAP SNC. |
|
| This validation check checks that the currency used in the purchase order confirmation received from a supplier back-end system is the same as the currency used in the purchase order in SAP SNC. |
|
| This validation check is relevant for confirmations ( |
|
| This validation check is relevant for confirmations ( |
|
| This validation check is relevant for confirmations ( |
|
| This validation check is relevant for confirmations ( |
|
| This validation check enables the functionality for handling partial purchase order confirmations (confirmations that do not contain all the items in a purchase order) via a |