.png)
In production, resources such as machines and gates can now be directly linked to their associated storage locations - dedicated fields are available for inbound buffer, outbound buffer, and a general storage location. In addition, a new validation protects against cyclical recipe references, and for the first time, recipes can be linked directly to workflows, making them evaluable across interfaces.
When a production machine or loading gate is assigned to a specific storage location, this information previously often had to be represented via a workaround using flex parameters - error-prone and hard for new employees to follow. The direct assignment of inbound buffer, outbound buffer, and general storage location on the resource makes this detour unnecessary: production managers see at a glance which storage locations belong to which machine, and the assignment can be maintained via a convenient search page instead of technical parameters. This reduces onboarding effort and lowers the risk of misassignments in warehouse logistics around production. The new validation of cyclical recipes addresses a problem that could quickly lead to inconsistent or even uncalculatable recipes in complex recipe structures with multiple nesting levels. If a circular reference is detected, the system immediately informs those responsible for the recipe upon saving, instead of the problem only being noticed at the next calculation. The new linking of recipes with workflows, in turn, makes it possible to couple approval processes and quality checks directly to the respective recipe and evaluate them accordingly.
You activate the storage location fields on the resource via the associated UI configurations in the resource screen; inbound buffer, outbound buffer, and general storage location can then each be selected via a search page. Validation of cyclical recipes is automatically active as soon as a recipe, an item with a recipe, or a recipe line item is saved. If a circular reference is detected, an error message appears with a reference to the affected link. Linking recipes with workflows is done via the new foreign key field directly in the enquiry screen; once linked, the assignment can be selected in evaluations and reports. For companies with deeply nested recipe structures, a one-time check run across the recipe inventory is recommended to identify already existing, previously undetected cyclical references.
