# Basic Setup#

## Mandatory field check#

The mandatory field check allows to define customer-specific mandatory fields to support the creation of master or document data. Certain values are predefined, which are checked after the input is completed. Here a mandatory field can be defined in dependence to other fields with the result:

Cancel: The fields must be filled Note: The fields can be filled

You can set up mandatory field validation for the following data: Master data:

• Article
• Debtor
• Vendor
• G/L account
• Resource
• Workplace
• Workstation group

Document data:

• Service header, service item line and service line
• Delivery schedule

A "Variable mandatory field check" can be activated for the master data, e.g. of the articles. I.e. fields can be defined individually, which must be compellingly indicated by the user with new creation or change of master data. Only when all entries are complete, the master data record can be marked with "Maintenance completed" or the document can be "Released" and used in the system (e.g. when posting a delivery).

The check for completeness of the information is performed as soon as the user sets the Maintenance field in the respective master data card to the value "Maintenance completed", or via the "End article maintenance" function.

If not all mandatory fields have been filled in, an error message or a note appears, depending on the configuration of the individual mandatory field. After "Maintenance completed" has been entered, the fields of the master data record can no longer be changed. However, connected tables (e.g. remarks) can still be changed.

To be able to edit the master data record again, select the function - "Edit article".

### Mandatory field check setup#

The use of the mandatory field validation can be activated separately for the individual areas:
For articles In stock facility
For accounts receivable, sales header and lines In Accounts Receivable & Sales Setup
For G/L accounts In financial accounting setup
For resources In resources facility
For workstation groups and workstations in production facility
For scheduling agreement headers In scheduling agreement setup
For service In service facility

### Setup mandatory fields#

The mandatory fields are defined via the application search "Mandatory fields setup tables".

When called, the "Mandatory fields setup tables" are opened. In this list, the corresponding checks can be viewed per table

From the list of checks, the existing checks can be edited or new checks can be added.

This chapter explains how to create checks for a table and the parameters required for a check.

Click on "New" to create a new test record.

Field Description
Table no. This field contains the number of the table for which this check is intended.
Table name This field contains the description of the table for which this check is intended and is
Number of fields Specifies the number of condition fields automatically

Via the menu item "Mandatory fields" you can define the mandatory fields for the corresponding test record.

Then select the "New" menu item on the "Mandatory fields card" to define the corresponding mandatory fields for the desired test record.

The mandatory field map opens. The mandatory field map consists of three info tabs: "General", "Field definition" and "Condition definition". These areas and their meaning are explained below.

#### Inforegister General#

Field Description
Table no. The table no. is automatically filled with the table no. that has already been defined in the test record in the "Table no." field.
Action The "Action" field is used to control what type of check it is. The following selection options are available:

Note:
If the check is defined as "Note", the user will receive a note message when processing the mandatory field check. However, this message does not influence the release of master data or documents. It is rather to be seen as information, with the help of which the user can still add data, which may be informative, but is not mandatory for processes.

Abort:
If a check is defined as "abort", an abort message follows with the processing of the mandatory field check. This means that the release of master data or documents cannot be completed because process-relevant information is missing.
##### Info tab Field definition#

In the "Field definition" info tab you can set up the check for a mandatory field using the table below.

Field Description
Field no. This field contains the number of the field for which this check is intended
Field name This field contains the description of the field for which this check is intended and is automatically filled when the "Field no." is assigned.
Comparison type The "Comparison type" field serves as a comparison operator, with which the value of the field in the data set is checked against the value from the "Comparison value" and / or "Maximum comparison value" fields. The following comparison operators are available here:
<>
=
>
<
>=
<=
>=<=

Note
Depending on the definition of the "Comparison value" and "Maximum comparison value" fields, the selection of the comparison operator may be limited
Comparative value The "Comparison value" field checks the value of the field in the record in dependence with the "Comparison type" field
Maximum comparison value The "Maximum comparison value" field checks the value of the field in the record in dependence with the "Comparison type" field
when selecting the comparison type ">=<=". Thus it is possible to define from-to ranges.
Here, the "Comparison value" field takes the "from role" and the "Maximum comparison value" field takes the "to role".

Note - This input is provided for computable operands only.

Example:
You want to set a mandatory field check for the "Description" field in table 27 (Articles) so that the Description field must always contain a value. Otherwise, the user would receive a hint or abort message.

For this purpose, the "Description" field with the number "3" is specified in the "Field no." field. The operator "<> " is used as comparison type and the field "Comparison value would contain "" (empty, no entry).

#### Inforegister condition definition#

In the "Condition definitions" info tab, you can further restrict the mandatory field range using the table below.

Field Description
Condition Field no: Specification of the field on which the condition is to be checked
Condition field name This field contains the description of the field for which this condition is intended and is automatically filled when the "Condition Field No." is assigned.
Comparison type Condition The "Comparison type condition" field serves as a comparison operator, with which the value of the field in the data set is checked against the value from the "Value condition" and / or "Maximum condition value" fields. The following comparison operators are available here:
<>
=
>
<
>=
<=
>=<=

Note
Depending on the definition of the "Value condition" and "Maximum condition value" fields, the selection of the comparison operator may be limited
Value condition The "Value condition" field checks the value of the field in the record in dependence with the "Comparison type condition" field
Maximum condition value The "Maximum condition value" field checks the value of the field in the record in dependence with the "Comparison type condition" field when the comparison type ">=<=" is selected. Thus it is possible to define from-to ranges.
Here, the "Comparison value" field takes the "from role" and the "Maximum comparison value" field takes the "to role".

Note
This input is provided for computable operands only.

Example:
In the previous example, a mandatory field check has been set on table "27" (Items). In the field definitions, the check has been set to the "Description = " field. As a result, each item must contain a value in the "Description" field. Otherwise, the user would contain a hint or abort message.

If you now want to restrict that the description should only contain a value for certain articles, e.g. if it is a production article, this is to be set up in the "Condition definition" info tab as follows:

For this purpose, the "Procurement method" field with the number "5419" is specified in the "Condition field no." field. As comparison type the operator "=" is used and the field "Value condition would contain the value "1" (production order.

Then confirm your setup with "OK".

## Notes in documents / master data#

Field Description
Locked/Locked (User) Field that activates the lock of the master record (as before). However, the field can now no longer be changed directly.
Locked (user) Here the master record can now be locked by the user. The value is transferred to the Locked/Locked (user) field if the master record is not locked by the mandatory field check or maintenance is locked.
When maintenance is complete, the lock is transferred back to the Locked field by the user.
Care This indicates whether the record is currently in maintenance or not.
Status mandatory field check This field displays whether the mandatory field check was not performed (no check), completely checked, or incompletely checked.

Note:
The lookup on the field can be used to view the missing required fields.
Locked from This shows whether the record is locked by the mandatory field check or by the user.