
6.2-r13	release/6.2.x	2021-11-26T13:30:40Z		6.2.11	6.2.12	6.2.13	9 / 55	6.2-r13.zip 6.2-r13.zip
6.2-r13 What's new? `Forecast` - When the product is seasonal and with many zeros override the expert selection with the salt forecast model DEV-2945 , PR-2258 `Forecast` - Include trend column in forecasts table for more detailed breakdown column DEV-2969, PR-2258 `Forecast` - Model description logged in the forecast table DEV-3018, PR-2258 `Forecast` - If skip forecast to date is set then the "removing leading zeros" functionality will be ignored, i.e. zero sales in the beginning of sale history are included in forecast calculations DEV-2360, PR-2258 `Forecast` - New forecast log and accuracy tracking, can be found in a new workspace called Forecast Accuracy Tracking and is only accessible to a system user. DEV-2632, PR-2378 `Demand calculations` - Adding origin trace so you can see from which block of demand the items came and also adding a customizable order matrix that can be used to populate a custom demand matrix DEV-2740, PR-2403 `Orders` - Floating Order Frequency: This solution introduces a new field for floating order frequency. It is applied in the following manner: Using the standard order logic, AGR checks if it should order an item, and if so, it calculates the quantity using the floating order frequency to achieve a longer order period. PR-2463, DEV-1993 `Orders` - Special Order Items: New column introduced that can be used to mark special order items (either through data mapping or a workspace). Another type of order logic runs for the items that are marked as special order items that utilize a new demand formula only designated for these items. These items would ignore the global order logic settings (min/max or default) and always just order the demand based on this formula. By default, the special order demand formula is Sales Orders +Promotions but that can be configured in the database. PR-2463, DEV-2319 `Orders` - Introducing thresholds (Minimum order multiple threshold) into the order logic. Calculated order quantity in an order proposal must exceed the percentage of the order multiple to be rounded up. Can be configured globally or for individual items. (Example: An item has order multiple = 10 and calculated quantity = 14 units, thus 40% of the next order multiple. With a 30% threshold, AGR will suggest 20 units but with a 50% threshold AGR will round down to 10 units) PR-2463, DEV-2983 Database Update Scripts Check out the update reports for updating and patching in the dbscripts\comparereports folder of the release zip file. (Note that all schema changes listed in the patch reports are applied every time you patch the databases, so please check the report and see if you have any customizations in the objects listed there.) Known Issues/Bugs Unaddressed issues in JIRA Issues Issues that were addressed and fixed in this release See list on Jira See list of pull requests involved in this update on GitHub See code changes on GitHub compare Client 6.2.10 `Item Card` - Remove the series data description on the tooltip in the Item Card chart. This description would only appear in the tooltip if it existed and there was only a single series (point) in the tooltip (on the x axis). DEV-2651, PR-2118 `Workspaces` - Fix: Move to next cell after TAB in insert action. DEV-2413, PR-2151 `Grids / Reports` - Fix the formatting of grouped date columns. The sorting of grouped columns (which this issue is part of) had already been fixed by @agr-asta but the formatting of grouped date columns required a slight fix. DEV-2400, PR-2115 `Workspaces` - fix: calculated columns should not have any aggregation options available in view settings. DEV-2749, PR-2122 `Grids` - Add `Autosize This Column (Skip Header)`, `Autosize All Columns (Skip Header)` and `Size To Fit` options to the grid column menu in the Item Card Grid, Reports Grid, Report List Grid and Orders Grid. The autosize option calculate the minimum width required to display column dat, the `skip header` option does the same but ignores the size of the column header. Size to fit utilises the horizontal space available for the grid to display the columns. DEV-1994, PR-2111 `Login` - Fix: login redirecting directly to dashboard even though the user doesn't have access to it resulting in ugly error DEV-2723, PR-2145 `Scheduler` - Fix: issue with schedule object was not saved correctly with scheduled tasks DEV-2802, PR-2211 `Grids` - Fix the sorting when columns are grouped and the user tries to sort on multiple columns. DEV-2987, PR-2261 `Error Message` - Change error message pages and removing the cat references DEV-2381, PR-2290 `Grids` - Fix position of column menu when it is far right on the screen (< 300 px from the right edge of the browser window). This was a problem after the width of the menu grew when adding new auto sizing options for the columns. DEV-1994, PR-2287 `Workspaces` - Increase the queried range of period filter options to -100, +100 years. This is an extreme upper/lower range limit, the actual limit is determined by the available values in the database date table. PR-2296, DEV-2316 `Reports/Items` - Fix issues with not being able to remove columns from reports when two columns have the same name but different id's PR-2342, DEV-3031 `Workspaces` - Fix a filter and sorting bug in Workspaces PR-2346, DEV-3032 `Reports/Items` - Fix: Lead time and additional lead time, in filters, are displayed as text in items and reports PR-2385, DEV-3038 `Orders` - Fix: Orders views look "unsaved" after adding a column to orderviewcolumns + sidebar PR-2404, DEV-2951 `Workspaces` - Adding config options for links within workspaces to be able to open a linked view in another tab and apply conditions for what lines should display links. This change also adds the ability to link between workspaces. PR-2435, DEV-3063, DEV-3062 Api 6.2.11 `Scheduler` - Use AGR scheduler instead of SQL Agent for db stats save DEV-2615, PR-2128 `Forecast` - Fix issues with the parallel process: The hanging of the parallel process and Removed the need for the /type parameter, it will be optional now. If not supplied it will be read from the forecast_type setting in the db DEV-2663, PR-2177 `Forecast` - Capture std-error output from forecast executables DEV-2531, PR-2143 `Forecast` - When the product is seasonal and with many zeros override the expert selection with the salt forecast model DEV-2945 , PR-2258 `Forecast` - Include trend column in forecasts table for more detailed breakdown column DEV-2969, PR-2258 `Forecast` - Model description logged in the forecast table DEV-3018, PR-2258 `Forecast` - If skip forecast to date is set then the "removing leading zeros" functionality is ignored DEV-2360, PR-2258 Databases 6.2.12 `Allocation` - Allocation module stabilization DEV-2774, DEV-2986, PR-2120, PR-2498, DEV-2356, `Promotions` - Promotions module stabilization DEV-2782, DEV-2771, DEV-2412, PR-2124, PR-2125, PR-2979 `Item Card` - Item Chart performance improvements: Precalculating stocks and undelivered today, introducing caching mechanism DEV-2709, DEV-2944, PR-2047, PR-2195 `Scheduler` - Use AGR scheduler instead of SQL Agent for db stats save DEV-2615, PR-2128 `MBE` - fix: The standard MBE fields MAPE and MAPE CATEGORY retain outdated values DEV-2800, PR-2166 `Connected items` - fix: an error happened when opening the calendar for "Connect from" / "Connect to" and then clicking the "x" button. DEV-2830, PR-2175 `db stats` - Incorporate disk latency stats into the zys.stats concept DEV-2707, PR-2169 `Data transfer` - Using system tables to get column info instead of information_schema due to poor performance DEV-2929, PR-2186 `Split Orders` - fix: Case sensitive error in ordersplitcalculate DEV-2927, PR-2196 `Data transfer` - Cleanup of elements that were accidentally copied into 6.2 but should only be in 6.3 and a migration to delete those elements DEV-2835, PR-2223 `Demand formula` - Fixing demand formula, moving planner promo out of the coalesce DEV-2841, PR-2224 `Data Mapping` - Adding a Document Type filtering for sales orders for nav and bc data mapping DEV-3004, PR-2302 `Data transfer` - Adding a way to run a single layer of staging elements and also adding a debug to get execute statements to run manually DEV-2948, PR-2295 `Data transfer` - Improvements of `create_erp_table` procedure DEV-2990, PR-2298 `Data transfer` - Adding inv cus item details populate procedure for an already existing stg element and fixing stg element parameters DEV-3017, PR-2326 `MBE` - remove obsolete columns `days_until_stockout` and `days_in_stock` from MBE DEV-2847, PR-2292 `Data transfer` - Adding the concept of a virtual location, allowing users to have locations that will not show up in prod but be available in stg for mapping of transactions, undelivered etc. DEV-2666, PR-2345 `Data mapping` - Removing vendor lead time from transfer order lead time coalesce in raw datamapping DEV-2966, PR-2370 `Forecast` - Removing forecast foreign keys DEV-3027, PR-2362 `Data mapping` - Adding responsible column to product assortment to use on sku level DEV-3001, PR-2372 `Forecast` - New forecast log and accuracy tracking, can be found in a new workspace called Forecast Accuracy Tracking and is only accessible to a system user. DEV-2632, PR-2378 `Forecast` - Performance improvements - speed improvements by reducing item set DEV-2663, PR-2365 `Workspaces` - Log slow dynamic update queries DEV-2977, PR-2387 `Forecast` - Standard stg elements included with setup to help with forecast configurations DEV-2721, PR-2365 `Data Mapping` - Remove those prep and raw tables and views that only belong to the LFP, and add them to the LFP project DEV-3013, PR-2377 `Dynamic Forecasts` - fixing dynamic forecast timeout bug + initialize dynamic forc with trend + model description. Also fixing item group histories sale not merging correctly in dynamic forecast run group DEV-2706, PR-2389 `Demand calculations` - Adding origin trace so you can see from which block of demand the items came and also adding a customizable order matrix that can be used to populate a custom demand matrix DEV-2740, PR-2403 `Data Mapping` - Preventing duplicate primary routes between transfer order routes and purchase order routes. If duplicates are found, the transfer order route will prevail. PR-2409, DEV-2967 `Orders` - Fixing datatype of cost price for accuracy purposes. PR-2466, DEV-3112 `Orders` - Floating Order Frequency: This solution introduces a new field for floating order frequency. It is applied in the following manner: Using the standard order logic, AGR checks if it should order an item, and if so, it calculates the quantity using the floating order frequency to achieve a longer order period. PR-2463, DEV-1993 `Orders` - Special Order Items: New column introduced that can be used to mark special order items (either through data mapping or a workspace). Another type of order logic runs for the items that are marked as special order items that utilize a new demand formula only designated for these items. These items would ignore the global order logic settings (min/max or default) and always just order the demand based on this formula. By default, the special order demand formula is Sales Orders +Promotions but that can be configured in the database. PR-2463, DEV-2319 `Orders` - Introducing thresholds (Minimum order multiple threshold) into the order logic. Calculated order quantity in an order proposal must exceed the percentage of the order multiple to be rounded up. Can be configured globally or for individual items. (Example: An item has order multiple = 10 and calculated quantity = 14 units, thus 40% of the next order multiple. With a 30% threshold, AGR will suggest 20 units but with a 50% threshold AGR will round down to 10 units) PR-2463, DEV-2983

6.2-r13

What's new?

Forecast - When the product is seasonal and with many zeros override the expert selection with the salt forecast model DEV-2945 , PR-2258
Forecast - Include trend column in forecasts table for more detailed breakdown column DEV-2969, PR-2258
Forecast - Model description logged in the forecast table DEV-3018, PR-2258
Forecast - If skip forecast to date is set then the "removing leading zeros" functionality will be ignored, i.e. zero sales in the beginning of sale history are included in forecast calculations DEV-2360, PR-2258
Forecast - New forecast log and accuracy tracking, can be found in a new workspace called Forecast Accuracy Tracking and is only accessible to a system user. DEV-2632, PR-2378
Demand calculations - Adding origin trace so you can see from which block of demand the items came and also adding a customizable order matrix that can be used to populate a custom demand matrix DEV-2740, PR-2403
Orders - Floating Order Frequency: This solution introduces a new field for floating order frequency. It is applied in the following manner: Using the standard order logic, AGR checks if it should order an item, and if so, it calculates the quantity using the floating order frequency to achieve a longer order period. PR-2463, DEV-1993
Orders - Special Order Items: New column introduced that can be used to mark special order items (either through data mapping or a workspace). Another type of order logic runs for the items that are marked as special order items that utilize a new demand formula only designated for these items. These items would ignore the global order logic settings (min/max or default) and always just order the demand based on this formula. By default, the special order demand formula is Sales Orders +Promotions but that can be configured in the database. PR-2463, DEV-2319
Orders - Introducing thresholds (Minimum order multiple threshold) into the order logic. Calculated order quantity in an order proposal must exceed the percentage of the order multiple to be rounded up. Can be configured globally or for individual items. (Example: An item has order multiple = 10 and calculated quantity = 14 units, thus 40% of the next order multiple. With a 30% threshold, AGR will suggest 20 units but with a 50% threshold AGR will round down to 10 units) PR-2463, DEV-2983

Database Update Scripts

Check out the update reports for updating and patching in the dbscripts\comparereports folder of the release zip file. (Note that all schema changes listed in the patch reports are applied every time you patch the databases, so please check the report and see if you have any customizations in the objects listed there.)

Known Issues/Bugs

Unaddressed issues in JIRA

Issues

Issues that were addressed and fixed in this release

See list on Jira
See list of pull requests involved in this update on GitHub
See code changes on GitHub compare

Client 6.2.10

Item Card - Remove the series data description on the tooltip in the Item Card chart. This description would only appear in the tooltip if it existed and there was only a single series (point) in the tooltip (on the x axis). DEV-2651, PR-2118
Workspaces - Fix: Move to next cell after TAB in insert action. DEV-2413, PR-2151
Grids / Reports - Fix the formatting of grouped date columns. The sorting of grouped columns (which this issue is part of) had already been fixed by @agr-asta but the formatting of grouped date columns required a slight fix. DEV-2400, PR-2115
Workspaces - fix: calculated columns should not have any aggregation options available in view settings. DEV-2749, PR-2122
Grids - Add Autosize This Column (Skip Header), Autosize All Columns (Skip Header) and Size To Fit options to the grid column menu in the Item Card Grid, Reports Grid, Report List Grid and Orders Grid. The autosize option calculate the minimum width required to display column dat, the skip header option does the same but ignores the size of the column header. Size to fit utilises the horizontal space available for the grid to display the columns. DEV-1994, PR-2111
Login - Fix: login redirecting directly to dashboard even though the user doesn't have access to it resulting in ugly error DEV-2723, PR-2145
Scheduler - Fix: issue with schedule object was not saved correctly with scheduled tasks DEV-2802, PR-2211
Grids - Fix the sorting when columns are grouped and the user tries to sort on multiple columns. DEV-2987, PR-2261
Error Message - Change error message pages and removing the cat references DEV-2381, PR-2290
Grids - Fix position of column menu when it is far right on the screen (< 300 px from the right edge of the browser window). This was a problem after the width of the menu grew when adding new auto sizing options for the columns. DEV-1994, PR-2287
Workspaces - Increase the queried range of period filter options to -100, +100 years. This is an extreme upper/lower range limit, the actual limit is determined by the available values in the database date table. PR-2296, DEV-2316
Reports/Items - Fix issues with not being able to remove columns from reports when two columns have the same name but different id's PR-2342, DEV-3031
Workspaces - Fix a filter and sorting bug in Workspaces PR-2346, DEV-3032
Reports/Items - Fix: Lead time and additional lead time, in filters, are displayed as text in items and reports PR-2385, DEV-3038
Orders - Fix: Orders views look "unsaved" after adding a column to orderviewcolumns + sidebar PR-2404, DEV-2951
Workspaces - Adding config options for links within workspaces to be able to open a linked view in another tab and apply conditions for what lines should display links. This change also adds the ability to link between workspaces. PR-2435, DEV-3063, DEV-3062

Api 6.2.11

Scheduler - Use AGR scheduler instead of SQL Agent for db stats save DEV-2615, PR-2128
Forecast - Fix issues with the parallel process: The hanging of the parallel process and Removed the need for the /type parameter, it will be optional now. If not supplied it will be read from the forecast_type setting in the db DEV-2663, PR-2177
Forecast - Capture std-error output from forecast executables DEV-2531, PR-2143
Forecast - When the product is seasonal and with many zeros override the expert selection with the salt forecast model DEV-2945 , PR-2258
Forecast - Include trend column in forecasts table for more detailed breakdown column DEV-2969, PR-2258
Forecast - Model description logged in the forecast table DEV-3018, PR-2258
Forecast - If skip forecast to date is set then the "removing leading zeros" functionality is ignored DEV-2360, PR-2258

Databases 6.2.12

Allocation - Allocation module stabilization DEV-2774, DEV-2986, PR-2120, PR-2498, DEV-2356,
Promotions - Promotions module stabilization DEV-2782, DEV-2771, DEV-2412, PR-2124, PR-2125, PR-2979
Item Card - Item Chart performance improvements: Precalculating stocks and undelivered today, introducing caching mechanism DEV-2709, DEV-2944, PR-2047, PR-2195
Scheduler - Use AGR scheduler instead of SQL Agent for db stats save DEV-2615, PR-2128
MBE - fix: The standard MBE fields MAPE and MAPE CATEGORY retain outdated values DEV-2800, PR-2166
Connected items - fix: an error happened when opening the calendar for "Connect from" / "Connect to" and then clicking the "x" button. DEV-2830, PR-2175
db stats - Incorporate disk latency stats into the zys.stats concept DEV-2707, PR-2169
Data transfer - Using system tables to get column info instead of information_schema due to poor performance DEV-2929, PR-2186
Split Orders - fix: Case sensitive error in ordersplitcalculate DEV-2927, PR-2196
Data transfer - Cleanup of elements that were accidentally copied into 6.2 but should only be in 6.3 and a migration to delete those elements DEV-2835, PR-2223
Demand formula - Fixing demand formula, moving planner promo out of the coalesce DEV-2841, PR-2224
Data Mapping - Adding a Document Type filtering for sales orders for nav and bc data mapping DEV-3004, PR-2302
Data transfer - Adding a way to run a single layer of staging elements and also adding a debug to get execute statements to run manually DEV-2948, PR-2295
Data transfer - Improvements of create_erp_table procedure DEV-2990, PR-2298
Data transfer - Adding inv cus item details populate procedure for an already existing stg element and fixing stg element parameters DEV-3017, PR-2326
MBE - remove obsolete columns days_until_stockout and days_in_stock from MBE DEV-2847, PR-2292
Data transfer - Adding the concept of a virtual location, allowing users to have locations that will not show up in prod but be available in stg for mapping of transactions, undelivered etc. DEV-2666, PR-2345
Data mapping - Removing vendor lead time from transfer order lead time coalesce in raw datamapping DEV-2966, PR-2370
Forecast - Removing forecast foreign keys DEV-3027, PR-2362
Data mapping - Adding responsible column to product assortment to use on sku level DEV-3001, PR-2372
Forecast - New forecast log and accuracy tracking, can be found in a new workspace called Forecast Accuracy Tracking and is only accessible to a system user. DEV-2632, PR-2378
Forecast - Performance improvements - speed improvements by reducing item set DEV-2663, PR-2365
Workspaces - Log slow dynamic update queries DEV-2977, PR-2387
Forecast - Standard stg elements included with setup to help with forecast configurations DEV-2721, PR-2365
Data Mapping - Remove those prep and raw tables and views that only belong to the LFP, and add them to the LFP project DEV-3013, PR-2377
Dynamic Forecasts - fixing dynamic forecast timeout bug + initialize dynamic forc with trend + model description. Also fixing item group histories sale not merging correctly in dynamic forecast run group DEV-2706, PR-2389
Demand calculations - Adding origin trace so you can see from which block of demand the items came and also adding a customizable order matrix that can be used to populate a custom demand matrix DEV-2740, PR-2403
Data Mapping - Preventing duplicate primary routes between transfer order routes and purchase order routes. If duplicates are found, the transfer order route will prevail. PR-2409, DEV-2967
Orders - Fixing datatype of cost price for accuracy purposes. PR-2466, DEV-3112
Orders - Floating Order Frequency: This solution introduces a new field for floating order frequency. It is applied in the following manner: Using the standard order logic, AGR checks if it should order an item, and if so, it calculates the quantity using the floating order frequency to achieve a longer order period. PR-2463, DEV-1993
Orders - Special Order Items: New column introduced that can be used to mark special order items (either through data mapping or a workspace). Another type of order logic runs for the items that are marked as special order items that utilize a new demand formula only designated for these items. These items would ignore the global order logic settings (min/max or default) and always just order the demand based on this formula. By default, the special order demand formula is Sales Orders +Promotions but that can be configured in the database. PR-2463, DEV-2319
Orders - Introducing thresholds (Minimum order multiple threshold) into the order logic. Calculated order quantity in an order proposal must exceed the percentage of the order multiple to be rounded up. Can be configured globally or for individual items. (Example: An item has order multiple = 10 and calculated quantity = 14 units, thus 40% of the next order multiple. With a 30% threshold, AGR will suggest 20 units but with a 50% threshold AGR will round down to 10 units) PR-2463, DEV-2983