Show TOC

 VSR Checks


In Warranty Claim Processing , VSR checks (VSR = validation/substitution rule) serve to check the validity of the data entered with a high degree of automation before it is saved to the database ( validation ) and to replace specific data ( substitution ). The checks can then be linked in to actions and be called automatically or manually in Warranty Processing depending on the settings in Customizing.

A validation comprises at least one step. Each step is composed of three components: prerequisite (optional), check and message. The check is only carried out when the prerequisite has been fulfilled. If the check runs up against an error, a predefined message is displayed.

A substitution comprises at least one step. Each step is composed of two components: prerequisite and substitution. The substitution is only carried out when the prerequisite has been fulfilled.

Note Note

If the system is to display messages for substitutions as well as validations you first have to create a validation with the same prerequisite for the appropriate substitution and also an inverse check (for this prerequisite). In the case of the substitution (i.e. prerequisite is fulfilled), the validation encounters an error and an appropriate message is displayed.

The standard actions for calling VSR checks therefore expect a validation for every substitution. If you want to work with substitutions without validation (and therefore without message), you have to program you own actions.

End of the note.

You can combine several terms to complex rules by using operators (for example, AND, OR). If you do not want to have to create the same rule every time with the editor, you can define and save rules per call-up point (see below), which are then available for every validation or substitution of this call-up point.


The VSR checks are identical to the VSR checks that are used in FI-SL Special Ledger .

You can find further information in the standard documentation under Validation, Substitution and Rules .


  • You create validations and substitutions for each call-up point in the application area warranty. Call-up points are specific places in an application at which the processing of a validation or substitution is called up. Data available for the validation and substitution depends on the call-up points.

    The possible call-up points in warranty claim processing result from the possible combinations of the following parameters (see also: Warranty Claim ):

    • Category: versions from claimant, versions to reimburser, versions from reimburser, versions to claimant

    • Claim level: header + version, defect code (on item level), entire item

      You can differentiate between 3 different call-up points for each combination.

  • The system can display a message as the result of a validation. If you assign a decision code to such a message, this code is set in the warranty claim as the result of the validation.

    If a validation checks whether an object still has a warranty and the result is negative, the system can display the message “There is no longer a warranty for the object”, for example, and then set the decision code Rejected in the warranty claim.

  • The default settings only allow warranty claim data to be evaluated. If you wish to link in other data, you have to enter your own exits in Customizing for Warranty Claim Processing under Start of the navigation path Control Data Next navigation step VSR Checks Next navigation step Define Client-Dependent User Exits. End of the navigation path

  • The validations and substitutions that you create are automatically called by the standard actions A006, A007, A016, A017, A026, A027 and A036. Action A006 Rule Engine Versions from Claimant (Time 1/2/3), for example, processes all the validations and substitutions one after the other that belong to the category Versions from Claimant , that perform checks on the data on header and version level and that have been defined for call-up points 1, 2 and 3.

  • There is one VSR check log each for the header and version-related checks, for the item-related checks and for the checks related to the defect code. In the standard layout you can find the first two logs on the tab page Version Detail, the third log on the tab page Item Detail . However, you can also place the check logs together on a separate tab page. You have screen groups S2220/2225, S7910 and S7915 at your disposal for this purpose.


  1. Create validations and substitutions and rules, if required, in Customizing for Warranty Claim Processing under Start of the navigation path ControlData Next navigation step VSR Checks End of the navigation path .

  2. Activate the VSR checks that are currently require ( transaction WTY_VSR_ACTIVE ).

  3. Include the VSR checks in the programming of your own action modules .


You can, for example, send all the claims from a specific dealer that contain an item with a value of over € 1000 to be processed manually. To do this, create a validation that finds the claims of this dealer as prerequisite and determines the items with a value of over € 1000 as check. Then create a substitution to define that the field Manual Processing in the claim is selected for these claims.