Docstoc

Define Validation

Document Sample
Define Validation Powered By Docstoc
					Define Validation
In this step, you define validation conditions for master data maintenance. The validation adds to the
options provided in the master data maintenance in

        the ability to define the screen layout

        the maintenance level and

        the use of default value

During the validation, certain input values are checked against one or more conditions defined by the user.
The validation runs after the first screen change after the entry is made. If the condition is met, the system
accepts the entered values. If it is not, the system outputs an error message. This error message can also
be specified by the user in the validation condition.

Example

In this way, you can determine, for example, that only certain depreciation keys are allowed for fixed assets
of one asset class.

Activities

Define validation conditions for master data maintenance according to your requirements:

         1. Choose function New entries
         2. Specify the company code and determine the check date by specifying

              o   the master data section (general master data = A, depreciation areas = B)

              o   the logical field group (screen)

              o   and the event description (1 = master data maintenance).

         3. Specify the key of the validation rule to be used.
         4. If you did not define a validation rule, you can define new rules:
                   a) Enter the company code and the key for your new validation rule.
                   b) Choose Goto -> Validation.
                   c) In the following screen, choose the function Create validation. Press ENTER.
                   d) Choose the function Insert entry.
                   e) Specify your validation rule by making the following specifications:

        Requirement under which the validation rule is to be checked.
        Check condition of the validation rule
        Error message to be output in case check condition is not met. You must create this error message
         yourself (transaction: SE61).

                  The creation of the requirement and the condition is supported by the function Fields for
                  requir.
                  Please also consider the F1 field help for the definition of the Boolean rule. There you will
                  find notes on the required syntax.
                  Caution
                  You have to make entries for the fields "company code," "asset class," "asset main
                  number/sub-number" using leading zeros. The system shows the length of these fields
                  when you use the function Fields for requir.
         5. Set the activation level in the definition of the validation condition.

Further notes

SAP Library FI-AA: Master Data -> Validations and Substitutions


Define Substitution
In this step, you define conditions for substitution for asset master data maintenance.

During substitution, certain entered values are checked against one or more condition(s) defined by the user.
If the condition is met, the system replaces the entered values with the values determined on the basis of
the conditions for substitution.

You can define substitution rules for the following points in time or activities:

        Creating assets

         Note that these substitution rules only take effect when you create assets (not when you change
         them). Assets that were created before the substitution rules were defined need to be changed
         later using a mass change to master data, if the change is required.

        Mass changes to master data

        Changing cost centers or business areas in the asset master record directly, with results as if an
         automatic transfer were performed (refer to Time-Independent Management).

         Here you can use the substitution to change the posting date of the automatically generated
         transfer document.

Example

You can specify in the substitution that when you create an asset and enter a certain business area, that the
system automatically enters a certain plant.

Activities

Define substitution conditions for master data maintenance according to your requirements, and assign them
to a company code:

         1. In order to define new substitution rules, choose the Substitution function in the initial screen.
                   a) Enter a name for the substitution.
                   b) Choose Substitution -> Create in order to use an existing substitution rule as a
                   reference.
                   c) Choose Insert entry.
                   d) Select the field for which an entry should be made automatically when the substitution
                   condition is fulfilled.
                   e) Specify your substitution rule by making the following entries:

        Substitution when prerequisite is met (constant value, field-to-field assignment, customer exit).
        Prerequisite under which the substitution rule is to be checked.

                   The Form Builder function supports the creation of prerequisites.
                   Set the substitution to active when defining substitution rules for creating assets.
         2. In order to assign the substitution rules to a company code, choose New entries in the initial
         screen.
                   a) Enter the company code and a key for the substitution rule.
                   b) For substitution rules for creating assets, you also have to enter the part of master data
                   that is affected (general data = A, depreciation areas = B) and the logical field group that
                   is affected.

For substituion rules for creating assets and changing organizational assignments, you can create only one
substitution rule for each company code (logical field group affected). On the other hand, for substitution
rules for mass changes, you can create a number of substitution rules in each company code. You can
distinguish among these rules by their sequential number.

Further notes

SAP library FI-AA: Master Data -> Validation and Substitution


Enter Chart-of-Deprec.-Dependent User Fields in Asset Class
Generally, the attributes for the asset class apply throughout the client, that is, for all charts of depreciation.
It is therefore sufficient to make these specifications once per asset class.

However, you can define certain country-specific attributes of the asset class, in addition to those that are
not country-specific. This means that the country-specific attributes are dependent on the chart of
depreciation. These attributes are:

        Control specifications (screen layout rule and account determination)

        Allocations (evaluation groups)

        Net worth valuation (property classification key)

        Insurance entries

You only need to carry out this step, if, contrary to the usual case, you want these attributes to be country-
specific (that is, different depending on the chart of depreciation). The system then uses the entries you
make here depending on the chart of depreciation in the given company code. The system then ignores the
attributes in the asset class that are independent of the chart of depreciation.

Standard settings

The asset classes supplied with the standard system do not have attributes that are specific to the chart of
depreciation.

Recommendation

In most cases, you do not need entries that are specific to the chart of depreciation.

Activities

Enter your chart-of-depreciation-specific attributes in the asset class, if needed.

Further notes

SAP library FI-AA: Organizational Elements -> Function of the Asset Class.