Comments
Hi Annika,currently dynamics locks the on hand components even if you enter a new sales order line with a earlier date. You have to do a full run. With CTP and also with CTP for planning optimization a newly entered line is added on top of the last run. That´s why you cannot run "simulate delivery dates" until the next periodic planning optimization run has been executed. This makes sure that delivery date control always takes all other demand into account to find a sutiable date. @Simon, how about making a reservation for order 1. Would that solve or at least improve your problem?Thanks for your ideas and feedback.Ben
4-4-5 is still common in manufacturing and retail and this prevents such businesses from leveraging recurring journals! This would be similar to where comparison periods are needed in financial report column definitions. Recurring journals need to be able to support non-monthly financial periods when defined in the Accounting Periods page.
We are using f&o, which is integrated with project operation, so there is a challenge in restricting users from feeling timesheets while they are already on leave for that day because we are not getting leave data in project operation.This is a basic requirement that needs to integrate leave absence with the project ops time sheet, so users are restricted from feeling the time sheet on leave and the same for restricted users to feel leave and absence when they have already filled out the timesheet for the same day.
The current order of this process makes no sense to me. Why would you send the notification to the recipient before you know if errors are going to occur? Either the notification should be triggered to the posting step or give a way fix the errors that occur (mentioned in other ideas posted on this board) without having to post the batch and then void all the lines and redo the whole batch.