Validation and substitution

Use

For the individual support of master data maintenance you can define validation and substitution conditions in Customizing for fixed assets (under Define Validation/Substitution).

Features

Validation

You create your own validation conditions, which serve as check rules when you create an asset master record. These customized check rules supplement the standard check rules. A validation condition consists of the following:

Company Code
Specification of the point in time for the check
Validation rule

A validation rule consists essentially of the following elements:

Condition, under which the rule should be checked (such as, if the asset class = LVA)
Check rule, that cannot be broken (such as depreciation key is GWG1 or GWG2)
Number of the error message that the system should produce if the check rule is violated

You must define check rules and conditions which conform to Boolean logic.

The system checks the validation conditions when you change to a new screen while creating an asset master record. If a check rule is violated, the system displays an error message. You specify the number of this error message in the validation rule. You have to create this error message yourself (transaction SE61).

The following figure shows Customizing definitions and application behavior for the validation rule: “Only depreciation keys for buildings are allowed in asset class 1000 and in depreciation area 01”:

This graphic is explained in the accompanying text.

Figure: Definition of a Validation

Substitution

You can use substitution functions within asset master data maintenance for the following activities:

Creating assets
Mass changes to asset master data (see Mass Changes to Master Data).
Changes to business area or cost center, with a resulting transfer document (refer to Changes to Master Data ).

Substitution for Creating Assets

Substitution conditions enable you to create default values, in addition to the defaults from the asset class. Substitution conditions are based on freely definable rules, and are dependent on different master data fields in the asset master record.

Example Example

You can use this method to complete the Business area field with corresponding values which is dependent upon the contents of the field Plant.

The rule would then be: "If the "Plant" field has the value XXXX, then replace the value 0000 (initial) in the "Business Area" field with the value YYYY.

End of the example.

Substitution conditions have the same structure as validation conditions. The most important part of the substitution is the substitution rule. A substitution rule consists primarily of the following:

The conditions under which the rule should be checked
Substitution if the requirements are met (setting of a constant value in a particular master record field). Or you can use a substitution exit with program code that determines the value to be entered in the master record field.

You define the substitution rules in Customizing for fixed assets. They are based on Boolean logic, as the validation rules are.

You can still change values that have been proposed on the basis of substitution rules. You can change these values manually in the master data transaction. Values that you change manually are not changed again by the substitution rule.

More Information

For information on the procedure to follow when creating validation or substitution rules, see the explanations in the Implementation Guide of Asset Accounting. For a detailed description of this topic, see the SAP Library in the application documentation for Special Ledger (FI-SL).