General 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 specified, which are checked after the input is completed.
At this point of the online help only the additional functionality of the mandatory field validation in KUMVISION factory365 will be explained. The general scope of functions is described here.
Mandatory field check setup#
| Area | Facility | Field |
|---|---|---|
| G/L accounts | Financial accounting institution | mandatory field check G/L account |
| Resources | Resources Setup | Compulsory field check Resource |
| 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 KUMVISION factory365 will be explained to you in more detail. The general 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 |
|---|---|
| FieldNo | 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 is used as a comparison operator to check the value of the field in the record against the value from the Comparison Value and/or Maximum Comparison Value fields. Here, the following comparison operators are available: - <> - = - > - < - >= - <= - >= Note Depending on the definition of the "Comparison Value" and "Maximum Comparison Value" fields, the selection of the comparison operator may be restricted |
| Comparison Value | The "Comparison Value" field checks the value of the field in the record in dependence with the "Comparison Type" field. |
| Reference Value Text | Gives the description of the selection in the Comparison Value field |
| Maximum comparison value | The field "Maximum comparison value" checks the value of the field in the record in dependence with the field "Comparison type" when selecting the comparison type ">=<=". Thus, it is possible to define from-to ranges. In this case, the "Comparison Value" field takes the "from role" and the "Maximum Comparison Value" field takes the "to role". Note - This input is intended for computable operands only. |
| Maximum Reference Value Text | Specifies the description of the selection in the "Maximum Comparison Value" field. |
| Condition Field No.: | Specifies 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 | The "Comparison Type" field is used as a comparison operator to check the value of the field in the record against the value from the "Condition Value" 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 restricted |
| Value Condition | The "Value Condition" field checks the value of the field in the record in dependence with the "Comparison Type Condition" |
| Condition Value Text | Provides the description of the selection in the Value 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. In this case, the "Comparison Value" field takes the "from role" and the "Maximum Comparison Value" field takes the "to role". Note This input is intended for computable operands only. |
| Condition Option Text | Indicates the description of the selection in the "Maximum Condition Value" field. |
| Action | The "Action" field controls what type of check is involved. The following selections are available: Note if the check is defined as a "Note", users will receive a note message when processing the mandatory field check. However, this hint message does not influence the release of master data or documents. It is to be seen rather as information, with whose assistance the AnwenderInnen can supplement still data, which are perhaps informative, but for processes not compellingly necessary. Cancel if a check is defined as "Cancel", then with the processing of the obligation field check an abort message follows. This means that the release of master data or documents cannot be completed because process-relevant information is missing. |
Note
At this point of the online help, only the setup of the check fields of the mandatory field check in KUMVISION factory365 will be explained to you in more detail. The general setup is described here.
Flexible reservation system#
With the help of the flexible reservation system, you can allow date conflicts in the reservation items, so that the links between the requirement originator and the requirement coverer are basically preserved, contrary to the Microsoft Dynamics 365 Business Central1 standard.
The date conflicts are also taken into account within the planning and remain despite "date conflict". A date conflict occurs in a reservation item as soon as the "Expected goods receipt date" is after the "Goods issue date".
Note
Basically, date conflicts within reservations should only exist for a short period of time and should be resolved promptly by date reconciliation and updating.
Company data#
You can activate or deactivate the flexible reservation system function in the company data via the "Allow date conflicts" switch.
Note
Please note that existing date conflicts must be cleared before deactivating the functionality.
Note
For an individual extension (e.g. user authorization) corresponding event triggers are available in the TechDocs.
Rolecenter#
The number of existing date conflicts is displayed in the Sales, Purchasing, Service, Projects and Production role centers. Via the function call within the respective batch, the reservation items are displayed and the documents can be called up and edited via the standard functionality of the reservations.
-
Microsoft, Microsoft Dynamics, and Microsoft Dynamics 365 are trademarks of the Microsoft group of companies. ↩