System Picks up wrong Asset valuation date
Our fiscal year is OCT- SEP. Asset Revaluation took place in FEB 2010.
To post revaluation, I use transaction ABAW and Transaction type 897 for the revaluation with Asset date FEB 2010. But when I run depreciation System posts new adjustment considering this revaluation occurred as in Oct 2009, First month of fiscal year. (Even I put Asset value date of FEB 2010 in ABAW)So I am getting error in new depreciation posting.
I donu2019t know why it is calculating revaluation based on Oct 2009 book value instead of Jan 2010.
I appreciate your valuable inputs.
Thank you.
Is that anything to do with period control settings?
Kindly let me know if someone knows about asset value date setting in period control data for revaluation.
Similar Messages
-
Good day,
I needed to create a new depreciation area in a live system. The depreciation area would not post to the GL, but would be used for tax purposes in a currency other than the local currency. When creating this area the asset values were translated at the system exchange rate which did not agree with the values of the manually maintained tax register. I proceeded by creating new transaction types that would only post to the new area, one of which was an asset disposal transaction, which would be used for downward adjustment of the APC value. I made my adjustments at the end of the previous financial year, but had to start over and proceeded to delete the depreciation area to allow me to start over.
After reinstating the depreciation area, my original adjustments were removed, however the assets which APC values needed to be adjusted downward using the disposal transaction, was giving me the AA 478 Posting transaction is not possible (value date not allowed) error.
I've reviewed the asset postings and there is no record of my original adjustment documents. The problem seems to be that field ANLA-ABGDT (Last Retirement Date), is still indicating the date of my previous adjustments and that this was not updated when the Depreciation Area was deleted and reinstated.
Again, I do not have any documents which I can access or reverse to update this table. Is there any way to clear this field without reversing the disposal document?
I'm also looking at implementing SAP note 1618286, to make error message AA478 a warning. I could not implement SAP note 533378 since it only supports component version 46c and we are currently running component verson 605.
I would appreciate your consideration of my problem.
Regards
MariusIf you are in Test System, you can use function module AA_AFABER_DELETE to totally delete the depreciation area (tcode SE37, specify chart of depreciation and depreciation area), After that recreate your depreciation area and run AFBN. But before you do that, have you created a retirement transaction type that limits the posting on your new depreciation area? If not create one.
Hope this helps.
Thanks!
Jhero -
Asset capitalisation date and depreceation date..
Dear all
I am facing one problem regarding asset capitalisation
date and depreciation start date.
In my project. one bus is purchased
in different component Ex . first they purchased
Engine , then
body , then assembly charges and then RTO registration .
Now ,
we booked in same asset no with all value , first i verified the invoice
for Engine in date 31.07.2007. asset value is debited with say
amount 500000 . than bill of body -amount 100000 at 30.11.2007 and
then assembly charges 50000 on 31.12.2007and than RTO registration
10000 on 05.01.2008.
Toatl asset vlue is debited by -
660000.
client want capitalisation date should be RTO
registration date which is 05.01.2008, so i make the change in asset
master Capitalisation date as 05.01.2008 because asset take value
from engine invoice verification date which was 31.07.2007.
Now
problem is, when i go for depreciation system calculate the depreciation
from 31.07.2007 even i changed the capitalisation date system calculate
the depreciation from the purchased date of Engine.
Is there
any configuration part where i have to make some change in Depreciation
start date or i am making some mistake.
Awaiting for your valuable
reaply.
Thanks in advance.Hi
For the same instead of creation of Direct asset the process to be followed is:
1.Create Asset under construction - AS01 with class AUC
2. Assign the same asset to your each transaction (From PO
to Registration Charges)
3.Create another Asset using AS01 with Final Class Vehicle
Use transaction code AIBU - Settle for settlment of asset under construction to Final Asset Vehicle and during settlment put the asset valuation date as 5.01.2008.
Also in Transaction code AIAB you have to put the Final asset i.e. Vehicle on which you are going to settle the asset under construction
But for the same the total reversal of your existing process is required.
Thanks & Regards
Mahesh
Edited by: Mahesh Nigudkar on Feb 9, 2008 7:07 AM -
Asset capitalization date not appropriate
Hi,,
Please tell me while I run Asset settlement through KO88 in period 7 ie, 22October 2010 asset capitalization and first acquisition date become 31.10.2010 instead of 22.10.2010. Because I executed asset settlement through KO88 on 22.10.2010 which is appearing 31.10.2010. What is the actual logic of taking advance value date instead of taking current date? Is it taking entire month and value is stamped on asset master as last day of month.....
Regards,
SamratDear Samrat,
when you enter the capitalization date manually the system uses this date as the default asset value
date when you post the first acquisition to the asset. If you do not enter a capitalization date in the asset master record, the system automatically adopts the asset value date of the first acquisition posting as the capitalization date. The system inserts the asset value date of the first acquisition posting in the capitalization date field (Capitalized on...) in the asset master record, when a capitalizing transaction type is used.
Please check your customizing in IMG: Asset Accounting > Transactions > Specify How Default Asset Value Date is Determined
The System logic with Asset capitilisation date is as follows:
When no capitalization date is entered in the asset master record the posting date of the first posting will be taken as the capitalization date not the asset value date.
Documentation:
R/3 Library:
Asser Accounting > Basic functions for transactions > Dates in Asset accounting
Default Values for Asset Value Date:
- Initial acquisition > Capitalization date from master record (if in
same FY, otherwise posting date)
- Settlement of AuC > Posting date
Set 'Prime Rule' and 'Alt.Rule' for each transaction (in your case it is
for transaction 'Settlement of AuC')
Regards Bernhard -
For some reason the system is telling me my birth date is wrong when it's not and it won't let me proceed to reset my password. Can someone tell me how to get a "real" person from tech on line?
contact itunes support
-
What is wrong with my Data Guard system?
What is wrong with my Data Guard system(10g10.2.0 on OEL5.0)? What method should I take to diagnose it and repair it?
After shutting down last night, my Data Guard does not run normally today.
On the primary database I issue the following commands:
DGMGRL> show configuration verbose;
Configuration
Name: sdb10g
Enabled: YES
Protection Mode: MaxAvailability
Fast-Start Failover: ENABLED
Databases:
sdb10g - Primary database
stdby10g - Physical standby database
- Fast-Start Failover target
Fast-Start Failover
Threshold: 30 seconds
Observer: hostp
Current status for "sdb10g":
Warning: ORA-16607: one or more databases have failed
DGMGRL> show fast_start failover;
show fast_start failover;
Syntax error before or at "fast_start"
SQL> startup
ORACLE instance started.
Database mounted.
ORA-16649: database will open after Data Guard broker has evaluated Fast-Start
Failover status
On the physical standby database I issue the commands:
SQL> startup mount
ORACLE instance started.
Database mounted.
SQL> recover managed standby database disconnect;
Media recovery complete.
DGMGRL> show configuration verbose;
Configuration
Name: sdb10g
Enabled: YES
Protection Mode: MaxAvailability
Fast-Start Failover: ENABLED
Databases:
sdb10g - Primary database
stdby10g - Physical standby database
- Fast-Start Failover target
Fast-Start Failover
Threshold: 30 seconds
Observer: hostp
Current status for "sdb10g":
Warning: ORA-16607: one or more databases have failed
DGMGRL> disable fast_start failover;
Error: ORA-01034: ORACLE not available
Failed.
Message was edited by:
frank.qian
null
nullThe primary database cannot be opened and the fast_start failover cannot be discabled:
SQL> SQL> ALTER DATABASE open
ERROR at line 1:
ORA-16649: database will open after Data Guard broker has evaluated Fast-Start
Failover status
DGMGRL> disable fast_start failover;
Error: ORA-01034: ORACLE not available -
Asset Value Date - Wrong posting
Dear All,
Company code is on live, Assets legacy data taken as on 31st-March-09.
Later we find that some of the assets [new purchases, in previous fiscal year (2008)] was not posted.
For that recently we posted that transactions F-90 using posting date is current date and document date is Actual acquisition date.
Due to document date in previous fiscal year system taten posting date as asset value date. So, depreciation posting missing for previous year.
I need your help. How can I rectify this???
Other than reversing the existing posting, what is the scenario????????
Thanx
Regards
parthaHi,
In order to post ,post capitalization please closed the previous asset accounting year.In ABNAN T.Code screen please update the original val date field with the date of the previous year from where you need to start calculating the dep. Doc date and posting date should be of the current FY.Also check T.Code Ao90 for updating the field Revenue from post capitalization with proper GL Account.
If your statutory audit for 2008-09 is not yet completed then you can think about T.Code AS91.While using T.Code ABNAN the following line items are generated.
Asset dr
Acc Dep cr
Rev form post capitalization cr
The system will only calculate dep of previous year.For the current year dep which are yet to be posted will be posted in the next schedule dep posting run.
Thanks
Monoj -
How to coorect a reversed document but wrong valuation date
Hello Experts,
We are on our closing activity right now.
But we have encountered a problem wherein we reversed a billing with corresponding issuance (601).The original posting has a valution date (sample: 7/23/2009) of the period we are closing, but the reversal has a valuation of the next period (Aug 3, 2009). Now the account connected to the reversal has gathererd the MAP for the next period (Aug 3, 2009).
So right now we are having a discrepancy on the Account connected to the transaction since different MAP are gathered since valuation date of the two transactions are not on the same period.
How can I solved this......?
Thanks Gurus.As you may be aware for any SD document, if corresponding Accounting Document is generated, then you cannot make any adjustments from SD side. It has to be addressed from FI side only where they have to pass JV
thanks
G. Lakshmipathi -
Consignement customer's invoice dates are fixed, but system is taking wrong
Hi All,
this is the consignement customer and for this customer invoice dates are given clearly stating as the 'end of month', but system is invoicing in the different dates. factory calender created and set and the maintenance in the customer master is also done. but why the system is creating invoice in different dates.Hi All,
this is the consignement customer and for this customer invoice dates are given clearly stating as the 'end of month', but system is invoicing in the different dates. factory calender created and set and the maintenance in the customer master is also done. but why the system is creating invoice in different dates. -
Substitution of Account Assignment from Asset Master Data
Hi Gurus,
System is not picking up cost center master data in FI document posting in the following scenario:
Posting in Asset through a transaction type which only post to non leading ledger, cost center is not getting populated in the FI document posted.
For the above issue, I have tried creating a substitution rule with a user exit, but system is not calling this substitution at all - Possible reason being the posting only in loacal ledger and fuction many not available for substituion to work in this situation. I may be wrong but looking at the system behaviour it is not calling the substition at all. I had activated total trace of the substitution but no substitution was called in this case.
In view of the about your expert advise is needed. I try checking BTE available for such situation but did not have any success yet. Any brilliant idea is welcome.
Thanks in advance for your help!!!hi Murlidhar Khatri ,
we use cost center assignment in our country, also. please use sap note 940758. when you use that sap note, you will send deppreciation costs to cost center which asset is assgined in master data.
sap note 940758:
In Asset Management it is only possible to enter one depreciation account for each asset class. However, depreciation should be posted to different functional accounts for the same asset class depending on the category of the cost center on the master data of the asset.
the link is :
[https://websmp101.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=940758&_NLANG=E]
best regards. -
Asset value date in case of multiple GRs
Hello All,
Could you please advise on the below issue.
I have created PO with one line item for quantity of 5 for acquiring 5 Fixed assets. Created 5 GRs with different dates as mentioned below
S.No. GR posting date Asset No.
1 18.08.2009 190698
2 28.08.2009 190699
3 10.08.2009 190700
4 06.08.2009 190701
5 03.08.2009 190702
In 1st asset capitalization taking 18.08.2009 which is Ok, for 2nd Asset also capitalization date taking as 18.08.2009 ( i.e. 1st GR date), for 3rd Asset capitalization date taking as 10.08.2009, for 4th Asset capitalization date taking as 06.08.2009 & for 5th Asset capitalization date taking as 03.08.2009. That means capitalization date it is taking as Oldest GR date. But essentially capitalization should pick from GR posting date (i.e.for 2nd asset it should take capilization date as 28.08.2009 instead of 18.08.2009).
Could anybody has clue why system is picking 1st GRN date when I have posted 2nd Asset.
Thanks a lot for your help in advance.
Regards
SrinivasHello
Please check the Document Date for the same
Thanks
Pramod -
Asset Value Date determination during settlement from Orders or WBS!
Hi,
I have a scenario on the asset value date and I am not sure what went wrong, asset side or CO side.
The scenario is as following:
1. Asset was converted into the system by 7/31/2008 with $10000.
2. The capitalized on date is 2/29/2008 on the asset master data.
3. On 8/31/ 2008, I charged $300 to an internal order and settled the $300 to this asset. The Asset Value Date on the Asset Explorer is 8/15/2008.
4. On 9/30/2008, I charged #500 to the same internal order and settled the $500 to this asset, the Asset value date on the asset explorer for this charge is still 8/15/2008.
This messed up the depreciation of this asset. Does anyone know how to control the asset value date from the settlement? Do we need to config in Asset side or in Order side? I want the $300 charge's value date is on 8/15/2008 and $500 value date on 9/15/2008. Is this possible?
Thanks,
TingIn the settlement you can fill in the asset values date.
The first posting is the basis for capitalization date(when you don't fill it in manual), when you fill it in for the second time the Asset Value Date it is no longer relefant.
This is only important when you have say in your depreciation key that the depreciation is based on days( see the help on this field) -
Asset acquisition date (How to change?)
Hi all,
As per http://www.jt77.com/financials/finan-15236.html
Asset capitalization date = 1day of depreciation calculation
Asset acquisition date = day of first cost allocation to the asset
Asset value date = date of effect in asset account of a posting
From the above dates, I would like to have a try to give my understanding on them.
Let say I have acquire an asset through a PO -> GR -> IR on 15 Oct 2007.
If I set the Cap Date as on 01 Nov 2007, and Asset Value date as on 01 Dec 2007, does this mean that ...
<u><i>Question 1:</i></u>
<b>My Asset depreciation will starts on Dec, with 2 months depreciation, which is Nov and Dec (because my Asset Cap Date is on 01 Nov 2007)?</b>
<u><i>Question 2:</i></u>
What if I want to <b>change the Asset acquisition date</b> to, say 01 Nov 2007?
I tried AB08 to reverse the asset, and change the GR posting date (through MIGO), and these date affect asset value date only.
I tried also to reverse the IR (using MR8M) and re-post the IR using Miro, with different Invoice and Posting date, these date only affect the FI documents.
I tried AS02, and I can only change Cap date, and NOT the acquisition date.
Please help on this, and clarify the usage / importance of the acquisition date.
As per AS03 (wrong first acquisition date)
Andreas Mann said that crucial is the "asset value date" (field BZDAT)it should be 31.05.2007, than first acquisition date is not importantCapitalization Date= Date on which the asset will be capitalized
Acqusition Date= Date on which first transaction is done on the asset after creation. It cannot be changed once a value is posted to the asset
Asset Value Date is important to determine the Depreciation
Asset value Date determines the postings to the asset. You can set the configuration for default asset value date. It is the date with which user wants to post to the asset, i.e it can be Document Date, Posting Date, Capitalization Date, Goods Receipt date. Check the list in
<b>Asset Accounting> Transactions> Specify How Default Asset Value Date is Determined</b>
Ordinary Depreciation Start Date Date on which the system starts calculates and posts depreciation
Ordinary Depreciation Start Date can be determined by the system through Priod controls defined or entered manually by the user. If entered manually it surpass the system calculated date. -
Group and Individual Assets Legacy data load
Hi, I work for a oil and gas company and I am having issues for the initial load for the group and individual assets into SAP .
Any help in regards to this would be helpful.
Below are the values that I would like to load into SAP for group ( grp 1 ) and individual assets ( Ind 1 and Ind 2 ) into SAP. We would like the depreciation to be carried on the group asset level and allocated on the NBV of individual assets ( which I think seems not possible but the standard allocates the depreciation only on acquisition value ) .
Asset APC Value Acc Depreciation NBV
grp 1 20,000.00 10,000.00 10,000.00
Ind 1 10,000.00 6,000.00 4,000.00
Ind 2 10,000.00 4,000.00 6,000.00
The problem is for intital load as well once the Ind 1 and Ind 2 are assigned to group asset grp 1 , it doesnt consider the acc depreciation at all , and the system allocations the accumulated depreciation based on apc values rather then NBV as of the load date.
Also, if I plan to load only the NBV of the group and individual assets only, the clients wants the APC values as well for reporting , so not where I can get those from if I only load the NBV.
Please let me know other approaches for initial load of group and individual assets that you guys might have worked on .
Thanks
bharanihi,
Hope your requirement is to see the takeover values as on legacy asset takeover date, for those group assets mistakenly created with AS21...instead of AS81.
Am i right...........
Then you can do this by doing below.
1) Go to OAAQ, for your CC, the last closed FY should be same as the FY, which is actually used during legacy asset upload.
2) now go to AS82, for your wrongly created group assets and in takeover values tab, enter the values manually.
Note: Assets created by AS01/AS21 can changed with AS92/AS82, then you will have takeover values tab in addition to normal AS02/AS22 transactions.
once updation is finished, then again revert back the changes in OAAQ.
This will solve your issue.
Thanks,
Srinu -
Asset Capitalisation date was from deleted PO
Hi,
Assets capitalised date shown on Assests Display was delete PO's capitalisation date.
Please advice why the asset didn't pick up the new PO date.
TQ
RegardsHi,
I am unable to change the deprecation date. Following was error message :
Dep.start date 01.02.2007 should no longer be changed (Please check)
Message no. AA930
Diagnosis
The ordinary depreciation start date 01.02.2007 has been changed. The depreciation start date is in a closed fiscal year. You cannot change depreciation in closed fiscal years.
System Response
The System allows this change. The depreciation start date is decisive for determining depreciation. This will be altered by the change, but only in the fiscal years which are still open, in other words from 01.07.2008.
Procedure
A. Confirm that you want to change the ordinary depreciation start date.
B. Check the expired useful life and correct this if necessary, because this also influences depreciation.
Maybe you are looking for
-
My brandnew earpod's controller doesn't work on my ipod touch.
So 3 days ago I bought earpods, when i got home and tried them on the controller didn't work so today I went to exchange them but the controller still doesn't work. I tried them on my ipad 2 and the controller works fine. Is there a way to install th
-
Is there a way to replace a page automatically in pdf document
how can i replace a page in pdf document automatically.
-
Too much time on network wait!
At peak time my apex pages are very very slow. I open Home>Utilities>Database Monitor>Sessions>Waits, and see all wait classes are network. I have already changed shared_servers to 100. But all waiting sessions are still waiting for network. How to i
-
Problem installing weblogic server 8.11
I have a problem while installing weblogic server 8.11 on a solaris 9 machine. I use the following instruction: ./filename.bin and I see the following message: Illegal instruction (memory dumped) (in french: instruction incorrecte (vidage memoire)) A
-
Our year end was on 31 March 2007 and since then lots of assets have been retired. The users will still have a display access on the Legacy system. Will the users be able to run their year end (31 March 2008) reporting on both systems should we dec