11.5.16

<< Click to Display Table of Contents >>

Navigation:  11.5 >

11.5.16

2019-09-30_9-42-46Project - SpecPage PDM

Version - 11.5.16.1

Planned Release Date - Mar/12/26

Features

Recipe report: In the recipe report, you can now include two existing recipe fields: Pre-def. % loss and Pre-def. loss. These columns are taken directly from the recipe (Recipe module, Recipe tab) and can be added to your report without any extra calculations. This helps you clearly show pre-defined losses when sharing specifications between factories.

Backend adjustments for recipe losses reporting. We have updated the database and reporting logic to properly support the Pre-def. % loss and Pre-def. loss fields in the recipe report. These technical changes ensure that the pre-defined loss values are saved correctly and can be shown on reports exactly as they are, without any additional calculations, when you send specifications between factories.

One-click costing method change and updated BOM costing report.

oIn Simulation → Variation, you can now change the costing method for all costing materials with a single click on the header above P1, P2, or P3 - just like in Recipe → Costing. When you click one of these columns, all items switch to the selected price set (P1, P2, or P3).

oThe BOM Costing report has been updated so that it reflects the currently selected price set, making it easier to generate reports using your chosen costing method.

Bug Fixes

Master Data.

oIn the partner structure, it was possible to delete an entire supplier folder (with all underlying partners) if all filters were deselected.

oChanges to partner ingredient text have not been saved. When changing an ingredient’s alternative trade designation or legal name for a specific partner, the change appeared temporarily but was lost after saving and reopening the material. As a result, exports still used the old text.

oIn Master Data → Ingredients, the context menu for translations showed two functions with the same name (Ctrl+F9 and F9). It was unclear which one translated all entries and which one only a single entry, and the text could not be adjusted via text components in Administration.

Administration. There have been three issues, related to Text components:

oVery long texts (over 4000 characters) produced an error message instead of a clear warning.

oCopying and pasting text between text components and external apps (such as Notes) did not work.

oThe bug report text could not be copied, and reports could not be downloaded directly.

Declaration.

oMissing material names in declaration printouts. After the update to version 11.5.15.1, some Declaration printouts no longer showed the material name, even though the name was visible and correctly set in PDM.

oWhen printing from the Declaration module with multiple ingredient lists (ILs), the system ignored the checkboxes: if you selected one or more ILs, the printout always included all ILs instead of only the selected ones.

Recipe.

oSearch for ingredient attributes showed no results. When you searched for ingredient attributes (by note or by selection), the system did not return any results, even though matching ingredients exist.

oAn access violation error appeared when saving a B-number. When this happened, users had to close PDM.

oWhen saving the Country/Group default setting in GDAs on a recipe and then creating a new variant, this “Save with recipe” setting was not carried over to the new variant.

Search.

oMissing nutritional values in search results. For some released recipes, the nutritional values were missing in the Search module. If the Recipe was generated manually, values appeared correctly, but otherwise the result was always 0.00.

oThe additional class (add.class) of ingredients was not displayed in the search results; the column remained empty.

oWhen creating a search in Master Data for Ingredient attributes using “Description + selection”, the selected values were not displayed correctly in the values table.

Looking forward to hear your feedback.

Thanks,

Team SpecPage PDM