Open jakaria42 opened 12 years ago
fixed asset schedule name can be same. no problem.
that mean, multiple table-1 entry is possible.
fixed asset will be distinguished by record id, not by project head id. So in our current system, i found no problem.
if user enters multiple table-1 entries, then in fixed asset manager, we will also show multiple rows as table-1 with different depreciation. that's never be a problem.
every record inserted as fixed will be treated as different fixed asset. the name/particular can be same, that will not create any problem. Is that seems okay to you?
I think, it will be best to have a different table for depreciation rates. This table will just like be the 'budget' table and have a direct relation with ProjectHead table.
If we do so, then is it possible to work with no 'depreciation rate' field in the 'record' table? I think it's not possible, if we allow users to change the depreciation rate from 'post' page. But I do think, that will not be a good idea.
I think we have a problem in the thinking of fixed asset schedule calculation.
In the fixed asset schedule, we have a column 'Opening Cost'. If we calculate fixed asset schedule for each items (say 'Table 1', not for a particular head), then how is it going to work?
Here is a scenario:
Solution: The only solution that comes to my mind is that we need to keep a certain depreciation rate for a certain head. What do you think?