Status-Dependent Check Framework
-
Checking for mandatory inputs
-
Locking fields against subsequent changes
Checking for Mandatory Inputs
Prerequisites
You have opened the current transaction (for example, a change document) in the WebClient UI and have activated the edit mode.
Context
The consistency check for mandatory inputs is not not only performed when you create new documents, but also later in the process. It can be executed on each status change.
-
Check for Fast Entry fields
- Check for business partners
- Check of texts
Some standard fields can be examined by the standard status-dependent check, but this framework can be used in user-defined fields as well.
-
Switch the current transaction to the next status either directly or by choosing the appropriate action.
The check is executed in the background. In case a mandatory input is missing, an error message is displayed.
- Correct the error by entering the missing value.
- Repeat the status change.
Locking Fields Against Subsequent Changes
Prerequisites
You have opened the current transaction (for example, a change document) in the WebClient UI.
Context
This functionality provides the possibility to lock fields against changes in a later status (later than the initial one).
-
Fast entry fields
- Business partners
Procedure
Activate the edit mode for the transaction or switch the transaction to a new status (while you are in edit mode). Several fields are still locked or get locked.