.png)
Resources now support fixed storage location assignments, cyclical recipes are automatically validated, and recipes can be linked to sequences.
Previously, if a production machine or loading gate was assigned to a specific storage location, this information often had to be mapped using a workaround with flex parameters – a process that was error-prone and difficult for new employees to understand. The direct assignment of inbound buffers, outbound buffers, and general storage locations to the resource eliminates this detour: production managers can see at a glance which storage locations belong to which machine, and the assignment can be maintained via a user-friendly search page instead of technical parameters. This reduces training time and lowers the risk of misassignments in production-related warehouse logistics. The new validation of cyclical recipes addresses a problem that could quickly lead to inconsistent or non-calculable recipes in complex structures with multiple nesting levels. If a circular reference is detected, the system notifies the recipe manager immediately upon saving, rather than waiting for the issue to be discovered during the next calculation. The new ability to link recipes with sequences allows approval processes and quality checks to be coupled directly to the respective recipe and evaluated accordingly.
You can activate the storage location fields on the resource via the corresponding UI configurations in the resource mask; subsequently, the inbound buffer, outbound buffer, and general storage location can each be selected via a search page. The validation of cyclical recipes is automatically active as soon as a recipe, an item with a recipe, or a recipe position is saved. If a circular reference is detected, an error message appears indicating the affected link. Recipes are linked to sequences via the new foreign key field directly in the enquiry mask; once linked, the assignment can be selected in evaluations and reports. For companies with deeply nested recipe structures, we recommend a one-time audit of the existing recipe database to identify any previously undetected cyclical references.
