Show TOC

 Validation Framework

Use

Before an ASN is converted into an inbound delivery in the inbound process, a validation framework checks its consistency against the appropriate purchase orders or scheduling agreement releases. The result of this consistency check is stored in a log assigned to the inbound delivery that is then created. The framework provides the user with the option of assigning and de-assigning the checks that are relevant for inbound processing.

Integration

This framework is used for most of the common inbound processing functions, such as creation of an inbound delivery or posting of the goods receipt. Validation framework for inbound deliveries is triggered when inbound deliveries are processed using:

  • Transaction VL60

  • IDoc processing

  • BAPI calls for processing inbound deliveries

Prerequisites

In Customizing for Service Parts Management (SPM) under Start of the navigation path Activate Enhancements for Service Parts Management (SPM) Next navigation step Activate Enhancements for Service Parts Management End of the navigation path , you must have activated Service Parts Management if you want to be able to use this validation framework.

Features

Validation checks and their results are configurable.

The following figure illustrates the validation framework functions in the inbound process:

Activities

When you trigger inbound delivery processing, validation is also triggered. You can follow these steps to set up a validation framework for any particular process:

  1. Defining a validation routine: the validation routine is the basic building block of the validation framework. This basic unit has access to ASN data and can perform certain checks and raise errors when the check fails. You can define a validation routine in Customizing for Service Parts Management (SPM) by choosing Extended Inbound Delivery Processing (SPM) -> Configure Inbound Validations -> Define Validation Routines.

  2. Grouping of individual checks into a validation profile: validation routines are grouped into a validation profile. This profile can then be assigned to a scenario (a combination of inbound actions, such as new ASN or posting goods receipt (GR), and system type, such as SAP ICH or SAP EWM).

    For each validation routine in a validation profile, you can:

    1. Activate or deactivate the validation routine

    2. Specify the action the system should take (for example, reject the inbound document or save it on hold) when the business check fails in the validation routine invoked in the validation stage.

      Standard validation routines and profiles that perform standard business checks on the inbound delivery document are provided as part of the system default settings. You can also create your own. You can define validation profiles in Customizing for Service Parts Management by choosing Extended Inbound Delivery Processing (SPM) -> Configure Inbound Validations -> Maintain Validation Profiles .

  3. Defining a required-field set: you can define a set of fields in an ASN as mandatory. This required-field set can be assigned to a scenario.

    The required-field set identifies the fields that are mandatory for an inbound delivery document. You can choose fields from the technical fields of the standard tables LIKP (Delivery Header) and LIPS (Delivery Item).

    Standard required-field sets are provided, as well as additional field sets that you can create in different situations. If you need to create your own required-field sets, create them in the Y* or Z* namespace.

    You can define required-field sets in Customizing for Service Parts Management (SPM) by choosing Start of the navigation path Extended Inbound Delivery Processing (SPM) Next navigation step Configure Inbound Validations Next navigation step Maintain Required Field Sets End of the navigation path .

  4. Assigning the required-field set and the validation profile to a scenario: you can assign the validation profile and the required-field set to a scenario. You can define a different validation profile and required-field set for the pre-validation and validation stages.

Results (pre-validation):

If the inbound document does not have a value in a field that belongs to the required-field set determined for the document for the pre-validation stage, the system rejects the inbound document.

If a validation routine that is active in the validation profile determined for an inbound delivery document for the pre-validation stage fails, the system rejects the inbound document.

Results (validation):

If, in the inbound delivery document, any of the fields assigned to the required-field set determined for the validation stage does not have a value, the system saves the inbound document with the status On Hold .

If a validation routine that is active in the validation profile determined for an inbound delivery document for the validation stage fails, the system saves the inbound document with the status On Hold or rejects the document, depending on the configuration for that routine in the profile.

You can make settings for the required-field set and the validation profile in Customizing for Service Parts Management (SPM) by choosing Start of the navigation path Extended Inbound Delivery Processing (SPM) Next navigation step Configure Inbound Validations Next navigation step Maintain Validation Profile and Req. Field Set Determination. End of the navigation path