on 05-19-2015 11:57 AM
Hi Expert,
We are creating the sub asset from main asset. after creation the sub asset system is picking the default useful life 9.8 years in one depreciation area 01. further depreciation area is copying correct useful life.
we have checked the screen layout and depreciation key also. because same dep key and screen layout is using another dep area also but they are picking correct useful life from main asset.
The question is why system is not copying useful life from main asset in only one dep area and from where system is picking default 9.8 years life.
Main Asset life :
Dep Area | Desc | Dep Key | Useful life | period | Odep start date |
1 | Book deprec. | ATVL | 5 | 8 | 01.04.2008 |
15 | Tax bal.sht. | ||||
18 | Company Act | ATVL | 4 | 8 | 01.04.2008 |
50 | Bef Comp 13 | ATVL | 3 | 8 | 01.04.2008 |
70 | Revaluation | ATVL | 2 | 8 | 01.04.2008 |
Dep Area | Desc | Dep Key | Useful life | period | Odep start date |
1 | Book deprec. | ATVL | 9 | 8 | 01.04.2008 |
15 | Tax bal.sht. | ||||
18 | Company Act | ATVL | 4 | 8 | 01.04.2008 |
50 | Bef Comp 13 | ATVL | 3 | 8 | 01.04.2008 |
70 | Revaluation | ATVL | 2 | 8 | 01.04.2008 |
Hi,
You say that screen layout is the same for all areas. However, screen layout is the most likely reason for the different behavior. So you should check it again. Also check that each area uses the same screen layout rule. If it is ensured that all areas are really using the same screen layout, you might check if there is some customer specific logic - e.g. a substitution - in place for area 01 that changes the useful life during asset creation.
Regards, Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sarvottam,
You say that after you enter the correct useful life and the "save" the subnumber, the value is reset to 9 years and 8 month even if you manually set the correct value before? This sounds very strange.
Normally we do not overwrite any manual input. So when you manually enter a useful life, the program will not change that value.
What you describe sounds like some customer specific issue. So there is no general answer for your question.
You will need to do some analysis to find out what is the reason. First you should try changing the useful life in AS02 after creating the subnumber. So you can find out if the problem exists only during creation or every time you change an asset. If the same problem exists in AS02, then substituions can not be the reason (because they are only called during creation). You will probably have to debug the program and set a watchpoint on fields xanlb-ndjar and -ndper to find out the program that changes the useful life.
Regards, Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
9 | |
9 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.