Scribd
Upload
42 views2 pages

What Are Validations

Validations check input values in SAP against rules to ensure only valid data is posted. You can create user-defined validations to check values and ranges of values beyond standard validations. A validation contains prerequisite and check statements in Boolean logic to validate data before it is posted. Matrix validations allow validating an entire document including header and lines. Validation messages inform users if input fails checks.

Uploaded by

Rashid Khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
42 views2 pages

What Are Validations

Validations check input values in SAP against rules to ensure only valid data is posted. You can create user-defined validations to check values and ranges of values beyond standard validations. A validation contains prerequisite and check statements in Boolean logic to validate data before it is posted. Matrix validations allow validating an entire document including header and lines. Validation messages inform users if input fails checks.

Uploaded by

Rashid Khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

What Are Validations?

In the SAP system, nearly all input values are validated by a program or against tables or master files.
Since some types of validations cannot be standardized, you can use the validations program to create
validations for your specific requirements.
The validation function enables you to check values and ranges of values as they are being entered in
the SAP system. Validation rules are stored in the Rule Manager. As data is entered into the system,
the Integration Manager validates the data against the validation rules. Because data is validated before
it is actually posted, only valid information is posted to the FI-SL application component.
Many values that you enter into the SAP system are automatically checked against standard validation
rules.

Example
The system validates account numbers against a master file or checks that a ledger is assigned to a
local company code.
You use validations when you want to create a user-defined Boolean statement to validate an entry in a
way that is not defined for the standard system. FI-SL validations allow you to create your own Boolean
statements without making any changes to the standard system.
A validation can consist of up to 999 steps. You can therefore validate data against any number of
Boolean statements before the data is posted.
A validation step contains the following statements:
 Prerequisite statement
The prerequisite statement determines whether the entered value(s) should be checked. If the
prerequisite statement is false, then the value is valid and the transaction continues.
 Check statement
The check statement determines whether the entered value(s) are valid. If the check statement is
true, then the value is valid and the transaction continues. If the check statement is false, the system
displays a message.
You define prerequisite and check statements using Boolean logic. You can define simple statements or
create complex statements using rules, user exits, and sets as part of the Boolean statement.
The following table shows examples of user-defined validations:
Prerequisite statement Check statement

If the account is a revenue account, then only sales centers can be posted.

If the currency is US dollars and the cost center is 100, then the business area must be 2 and the
plant must be 10.

If the user is contained in set RGUSER-02 and the currency then the account must be in set RGACCT-
is in set RGCUR-02, 02.

If the user and the currency are containedin the then the account must be in set RGACCT-
multidimension set USERCUR-02, 05.
The following graphic illustrates how FI-SL validations interact with values entering the SAP system:

For each validation step:


1. Data is entered into the SAP system.
2. Data is sent to the FI-SL Integration Manager and to validations.
Validations are part of the Integration Manager along with substitutions, ledger selection rules, and
summation rules.
3. Data is then checked against a prerequisite statement.
If the prerequisite statement is true, the data is checked against the check statement. If the
prerequisite statement is false, the data is valid.
4. If the prerequisite statement is true and the check statement is:
- True , then the data is valid
- False , then the system displays a message
You need to correct E (error) type messages before the value you are validating can be posted. You
should also correct W (warning) type messages. A (abend) type messages result in termination of
validation processing.
5. If there are additional steps in the validation process, the system repeats the steps described here.
For more information about creating Boolean statements, see Creating Boolean Statements for the FI-
SL System .
For more information about creating validations, see Creating a Validation .

Matrix Validations
You can also create matrix validations for certain callup points. Matrix validations allow you to execute
a validation for the complete document, including the document header and all document lines.

Example
You create a matrix validation to check that a certain combination of accounts is valid. The validation
compares the contents of each document line with all other document lines.
You can only use matrix validations together with callup point code 0003 within the Financial Accounting
(FI), Legal Consolidation (FI-LC), and Consolidation (EC-CS) application areas.

Validation Messages
When you create validations, you can also define the result of breaking the validation rule. You can
create the message and the message long text that should appear on the user's terminal if a check
statement is not met. You can instruct the system to send the user an information message or you can
require the user to correct the error before continuing with data entry.

Example
Suppose a user cannot post to cost center 200. When the user attempts to post to cost center 200, a
message appears and the user is not allowed to continue with processing.
For more information, see Validation Messages .

Link :-
https://help.sap.com/doc/f9bfd953189a424de10000000a174cb4/2.6/en-
US/25bed953189a424de10000000a174cb4.html

You might also like