Comments
Please add an option to retire a job - or mark it as inactive. Retired jobs should not be available in the list of jobs a new position can reference. Scenario: a customer has re-structured their jobs and titles and no longer wants to make use of the original jobs. All workers have be assigned new positions that reference the new jobs. The old jobs are referenced in previous positions of the workers and therefore cannot - and should not - be deleted. But it shouldn't be possible to reference them in any new positions. It is not enough to update the job description to 'DO NOT USE' - as many, both HR persons as well as managers requesting new positions - do not use the drop down, but simply enter the job id they remember.
There should be a way to edit/change job titles. There are few job titles with typo which is been used in positions, which we want to change or atleast apend with "Do not use". At the moment there is no standard provision for this in the system. Please provide this functionality so that the old titles can stay as it is after making the change.
As we have in org. management active positions and all positions it would be really useful to have the same lists for the jobs. In the job list, there is a button - manage changes, where we have a possibility to set an expiration date. However, expired jobs are still visible in the list and also they come up when we link a position with the job. So what is the purpose of having an expiration date in jobs?
Since the organizational needs are evolving, from time to time we add new jobs and eliminate old ones. Currently, the only way to hide expired jobs is to delete them from the list which also requires deleting the history from position details. I believe it is not the correct way to manage historical data.
My suggestion is to have two lists: active jobs and all jobs (where we will find expired jobs as well). So when the user will assign the job to the position an active list will be showing up.
Furthermore, if the inactive job is still needed then from manage changes a new time period will be set which will make a job active again.
I am sure this feature will enrich the job management process and make it easier to maintain jobs' data. Besides this feature will enable to keep the historical data in the position details.
We faced the same issue and unfortunately, could not identify the Job or fix the issue. Support suggested to delete all open transactions, which is not possible since many transactions have been approved through workflow.From system documentation, https://learn.microsoft.com/en-us/dynamics365/finance/general-ledger/configure-ledger It will take a few minutes for the account structures to be added and saved. When the changed account structure is saved to the ledger, the process to synchronize all the unposted transactions will begin. You must wait until the change is completed for the current ledger in the legal entity where the change is being made before you can make an account structure change for a ledger in another legal entity. Note that the account structures that you select must be active. Otherwise, the details of the account structures won't be effective in the legal entities where they are linked. Account structure activationWhen you are satisfied with your new setup or a change to an account structure, you must activate it. If an account structure is assigned to a ledger, this activation can be a long running process, as all unposted transactions in the system must be synced to the new structure. Posted transactions are not impacted by account structure changes.
Here the exact description of the current behavior: If we have a sales order line and a flexible batch reservation has been made for a sales order line AND then this line is mixed with other lines (without flexible batch reservation) in the work, the work is simply no longer carried out automatically despite the work template setting. It is then only possible to do this with the Warehouse Management App. Simply means that despite the work template setting (Valid Automatically process = Yes) the work is not carried out automatically. This work cannot be closed via the “All Work” module either. It is then only possible with the scanner.