Validation :The validation spews out an error message and cautions the end-user. The severity of the message can be mild which only warns but lets the end-user post the document. On the other hand, a validation can be configured to throw a serious error message and prevent incorrect posting.
A Validation is given a name and is assigned to a company code. A validation may checks data at document header level only (called as callup point 1) or at line item level ( called as callup point 2) or at the full document level ( call up point 3).
A given validation uses one of the above call up points.
A validation, at the minimum, contains three steps:
Step 1: a pre-requisite (validation will happen if the pre-requisite is met). If the pre-requisite is not met by the document under posting, the system ignores the validation technique and posts the document.
Step 2: If the pre-requisite is met a check is made for compliance of an extra condition (over and above the pre-requisite). If the condition is also complied with by the document, then posting happens.
Step 3: On the other hand, if the check activity is not complied with, then the system smells a rat and throws an appropriate error/warning message (depending on the severity of error as configured by you)
Substitution permits the customer-specific enhancement (substitution) of certain field contents.
Substitution consists of several steps (up to 999 are possible), each with two parts:
. Prerequisite
. Replacement
Substitutions are not supported by the document parking feature. Substitutions can only be made with posting transactions after turning parked documents into accounting documents.
Your validation contains a pre-requisite, Check and Message.
Your substitution contains a check and substitution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.