on
RE:
This is an important issue for me as I run into this for a fixed asset where the last depreciation run is month ago. Thus opening the period is not an option.
RE:
Sorry for the bad formatting in my other comment. The comment box supports rich text and the posted comment doesn't...
RE:
Great idea! Simple to implement and a big ease of use boost.A possible expansion: Also check the default location of the warehouse employee.So, when creating a warehouse document, check the following:Is there only one location? Then fill itDoes the current user have a default location in the warehouse employees? Then fill it
RE:
yes please - this would be more than just a nice to have!
RE:
Generally great idea!A company could also pre-define the company (brand) colors used ...
RE:
Agreed, seems like an unlikely design, considering the dedicated warehouse management filter codes, this change would allow for greater flexibility, since this parameter is the only option for affecting the load template ID if using "Automatically create at sales order entry"
RE:
This is a serious restriction when using DDMRP, as it does not allow us to generate order proposals projected into the future based on a sales forecast. In my opinion, the reason for this is that when calculating the buffer values, it is only possible to decide statically how many months should be used as past periods and forward periods. In order to calculate future requirements, however, the “Average Daily Usage” would have to be determined dynamically from the forecast, as no past periods exist for these future months.
RE:
It would make our daily work easier if we could save the lists.
RE:
To continue working efficiently and in a structured way, the use of stored lists is essential. We kindly ask you to restore this function as soon as possible.
RE:
Would that require that a planned production order or planned purchase order that is triggered by a sales quotation or project quotation may need an approval workflow to be firmed?