on
RE:
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.
RE:
This is actually a very needed functionality.
RE:
Please vote this idea - because of that MS spoiled standard Foreign currency revaluation in GL (you cannot reverse revaluation in a new year after closing previous year. Why? Because they introduced a fix, not for Poland, but for Italy and that fix now is refusing reversing foreign revaluation in a new year)
RE:
I was in process of raising exactly the same idea!
RE:
This is very much needed for my organization! Can something be done to allow scrolling in a tooltip?
RE:
Yes, we definitely need a PA activity! For example to build in an approval step for validating master data inside a pipeline.
RE:
For batch-based industries using batch attributes actively, specifically for customer specific attributes, inheriting all the batch information between companies is critical.
RE:
Thomas, keep in mind sorting on the fields depends on the key chosen by the system (not necessarly) the one selected by the programmer. This can affect your sorting order and yield wrong min/max
RE:
its a legal requirement in india under GST Law. As per law we can sent the Material/Goods or any other thing outside the business premises either on the basis of sales invoice or on the basis of challan.if material/goods or any other thing sent outside the organization on the basis of challan then it should be returned back with in 180 days otherwise GST input which we have availed on that item at the time of purchase that input we need to reversed or we need to pay the GST amount to the government as it will be treated as sales in that case.The same requirement exist in some other country also so its a must have functionality as otherwise business doing customization or handling all this manually which is very tough, costly and time consuming activity.