Mandatory field check#
You can use the mandatory field check to see whether a certain field has been filled in when you add or change base data, such as on a customer order.
KUMAVISION factory365 extends the mandatory field check of KUMAVISION base (BOOSTER) with the option of restricting the field to be checked and the condition. The comparison value is only checked if the condition is fulfilled.
At this point in the online help, only the additional functions of the mandatory field check in KUMAVISION factory365 are explained in more detail. The online help for the general business functions - mandatory field check of KUMAVISION base (BOOSTER) is described here.
Mandatory field check setup#
The use of the mandatory field check can be activated separately for the individual areas - analogous to the KUMAVISION base (BOOSTER):
| Area | Facility | Field |
|---|---|---|
| G/L accounts | Financial accounting institution | mandatory field check G/L account |
| workstation groups workstations |
production setup | mandatory field check workstation group mandatory field check workstation |
Delivery schedule headers |
Delivery schedule setup | Compulsory field check |
Note
At this point of the online help, only the additional setup options of the mandatory field check in KUMAVISION factory365 will be explained to you in more detail. The general mandatory field check setup options are described here.
Setup mandatory fields#
The mandatory fields are defined via the user search "Mandatory fields setup tables".
When called up, the "Mandatory fields setup tables" are opened. In this list, the corresponding tests can be viewed for each table.
You can define the mandatory fields for the corresponding exam record via the "Mandatory fields" menu item.
| Field | Description |
|---|---|
| Field No.* | Specifies the field that is to be set as a mandatory field. |
| Field Caption* | Specifies the name of the field that is to be set as a mandatory field. The "Field no." is automatically filled when assigned. |
| Compare Type | This field field is used as a comparison operator with which the value of the field in the data record is checked against the value from the "Comparison value" and / or "Comparison value maximum" fields. The following comparison operators are available:: - <> - = - > - < - >= - <= - >= Note Depending on the definition of the "Compare Value" and "Compare Value Max" fields, the selection of the comparison operator may be restricted. |
| Compare Value | This field checks the value of the field in the data record in relation to the "Compare type" field. |
| Reference Value Text | Gives the description of the selection in the Comparison Value field. |
| Compare Value Max | This field checks the value of the field in the data record depending on the Compare type field when the comparison type is selected ">=<=". This makes it possible to define from-to areas. The "Comparison value" field takes on the "from role" and the Compare Value Max field takes on the "to role". Note This input is only intended for calculable operands. |
| Max. Reference Value Text | Specifies the description of the selection in the Compare Value Max field. |
| Action* | This field is used to control the type of check. The following selection options are available: Notify If the check is defined as a Notify, users receive a hint message when the mandatory field check is processed. However, this notification does not affect the release of master data or documents. Rather, it should be seen as information that users can use to add data that may be informative but is not absolutely necessary for processes. Cancel If a check is defined as Cancel, an abort message is sent when the mandatory field check is processed. This means that the release of master data or documents cannot be completed because process-relevant information is missing. |
| Field No. (Condition) | Specifies the field for which the condition is to be checked. |
| Compare Type | This field field is used as a comparison operator with which the value of the field in the data record is checked against the value from the "Condition" and / or "Condition value maximum" fields. The following comparison operators are available: <> = > < >= <= >=<= Note Depending on the definition of the "Condition" and "Compare value maximum" fields, the selection of the comparison operator can be restricted. |
| Condition | This field checks the value of the field in the data record depending on the "Compare Type Condition" field. |
| Condition Value Text | Specifies the description of the selection in the "Condition" field. |
| Condition Max Value | This field checks the value of the field in the data record depending on the "Comparison type condition" field when the comparison type is selected ">=<=" is selected.This makes it possible to define from-to areas. The "Condition" field takes on the "from role" and the "Maximum condition value" field takes on the "to role". Note This input is only intended for calculable operands. |
| Condition Text | Specifies the description of the selection in the "Compare Value Max" field. |
* = KUMAVISION base (BOOSTER)
Note
When checking and/or setting conditions with reference to a text field, the SQL sorting must be observed.
The field length of a text field, for example, is not intended for checking and/or setting conditions.
Note
At this point of the online help, only the setup of the check fields of the mandatory field check in KUMAVISION factory365 will be explained to you in more detail. The general setup is described here.