When you instruct Microsoft Dynamics 365 Business Central to transfer production BOMs to Genesis R&D, the default behaviour is for ESHAPort to create only new recipes in Genesis. If you export a production BOM from Microsoft Dynamics 365 Business Central for which a recipe already exists in Genesis, ESHAPort skips it when importing data. Using this configuration, changes made to production BOMs in Microsoft Dynamics 365 Business Central for which a corresponding Genesis recipe already exists are not imported into Genesis during a data transfer.
If you want to update an existing Genesis recipe to reflect changes made in Microsoft Dynamics 365 Business Central, select the Recreate Recipes field on the Genesis Integration page before exporting data. When you transfer recipe data for a production BOM that currently has a corresponding recipe in Genesis, the system replaces rather than ignores the existing Genesis recipe. The current Genesis recipe is deleted and a new recipe is created in the database.
Note
When a Genesis recipe is deleted during the recreate process, Anywhere Mobility Solutions additional information associated with that recipe (such as nutritional overrides) is also deleted. Make sure you have set the correct filters for the BOMs you want to export before recreating recipes.