Hi GR, 1)We created a new field in the AssetBook table called "InitialAcquisitionDate - this is the one we use to retain what the original acq date is - system does not use it for anything.
The one I referred to as "last acquisition date" is really the "acquisitiondate" field. This one is populated by the system, each time an acquisition proposal journal is posted...So, by populating this field with the 12/31/06 date, in our implementation, it dated all acquisition journals as 12/31/06 - this is how we posted our original acquisition costs. Since acquisitions were posted in the same period, we didn't have to go back to previous periods. Since we uploaded accumulated deprecation balances, all in Dec06, we didn't have to go back prior periods to record each month's depreciation - that why we populated the "last depreciation run date with 12/31/06" - this way, the next journals generated for depreciation would be dated 01/31/2007. 2) We didn't use dummy COA, instead we have a clearing account we used for other items. We kept the Conversion profile in the system, since it's not being used for anything, it's just sort-of parked there. 3) With the new field, initial acquisition date, there would be no confusion since the dates will truly reflect the date the asset was acquired. This date never changes unless the user changes it. Users understand that the acquisition date (we renamed this to "last acquistion date") reflects the date of when any acquisition activity has been posted. On the service life, there are the two fields, on that holds what the original life time & then what's remaining. So, on the older assets, the life time remaining would be reduced by the number of months the asset has already been depreciated by. Hope this helps, --- In Axapta-Knowledge-Village@yahoogroups.com, G Radhakrishnan <[EMAIL PROTECTED]> wrote: > > Hi, > I have filledup the acquistion date as original date. > But after import, when you go for acquistion, the > system gives the date as 01/01/2006. As you told may > be my first period is from 2006. So If I keep period > much before it will take accordingly. . But this date > is taken as "Acquistion date" after posting the > journal but the "Depreciation run date" is same as I > kept in the excel sheet(In my case , say 10/01/1981). > I afraid this may lead cofusions for the users, right? > > Regards, > GR. > > > --- James Flavell <[EMAIL PROTECTED]> wrote: > > > Hi > > > > It is fine to load up assets as they oringally were > > and run aquistion and > > depreciation for these. The only thing is you will > > need ledger periods > > going back however far you want to post back in time > > (even if you setup your > > profile to debit and credit the same GL account). > > > > Not sure why you are getting 1/1/2006 but have you > > filled in the right > > aquistion date on the asset? Is 1/1/2006 the first > > ledger period you have > > in your system? > > > > > > -----Original Message----- > > From: Axapta-Knowledge-Village@yahoogroups.com > > [mailto:[EMAIL PROTECTED] On > > Behalf Of G > > Radhakrishnan > > Sent: 31 July 2007 10:15 > > To: Axapta-Knowledge-Village@yahoogroups.com > > Subject: Re: [Axapta-Knowledge-Village] Re: Fixed > > Asset - Acquistion > > > > Hi, > > Thanks a lot for your explanation. Can you please > > tel > > me something on the following points; > > > > 1. What do you mean by "last acquistion date" ? Is > > there any field available in this name ? Or u mean > > to > > say the "acquistion date" when you run the > > acquistion > > journal for the first time?i.e., immediately after > > import of assets. > > > > 2. What did you do with the "Conversion" profile > > Chart > > of Accounts after the acquistion and the > > depreciation > > till 31/12/2006. Because , these are just dummy COAs > > and will remain in the COA. > > > > 3. It is good that we will have the actual > > acquistion > > price; but I fear that the recent Assets; say assets > > acquired during 2001,2,3 will be having the > > acquistion > > date as 31/12/2006. So in a long run, say after 3 or > > 4 > > years, users should not think that the asset is > > acquired during 31/12/2006 having the service life > > say > > 19 years instead of actual 25 years..am i correct ? > > > > I did a piolet run yesterday on some assets of 1981. > > System does the following. > > > > Scenario is as follows- > > Asset dated 1981. > > Actual service life 25 years > > Depreciation Method - Reducing balance > > Depreciation frequency - Yearly > > > > After import,I acquired assets through GENERAL > > JOURNAL-Fixed asset journal - Acquistion proposal. > > > > System keeps the posting date as 01/01/2006. (Here , > > I > > didnt understand,why the date is coming as > > 01/01/2006 > > iinstead of anyother date or it is not asking for > > acquistion date) > > > > Posted all assets. The acquistion date is updated as > > 01/01/2006 where as the "Depreciation run date" is > > the > > date which i imported say 10/01/1981. > > > > I run depreciation after above step. System did the > > depreciation starting from 1981 till 2006 perfectly > > and it is posted on the respective posting profile. > > Now the "last depreciation run date" is 31/12/2006. > > > > Note that the service life remaining is automaticaly > > changed ; we need not put it manually. > > > > > > Is the above steps are fine ?? Expecting your reply > > reply pleaseeeeeeeeee > > > > Regards, > > GR. > > > > > > > > --- novembercalendar <[EMAIL PROTECTED]> > > wrote: > > > > > We implemented FA as of 12/31/2006. On our > > existing > > > assets, we used > > > the original acquisition date w/original acq amts, > > > original service > > > life, acq dates, & depr run dates. When we > > imported > > > the assets, we > > > used 12/31/06 for the "last acquisition date" and > > > for the "Date when > > > depreciation was last run". For service life > > > remaining> entered > > > life remaining after 12/31/06 depreciation. > > > > > > Using 12/31/2006 for the last acquisition date > > > allowed us to create > > > acquisition proposals/journals dated 12/31/06. > > > Then, for the next > > > time depreciation proposals are generated, the > > > system automatically > > > uses the next month's date. > > > > > > We set up a temporary profile called "Conversion" > > to > > > have all the gl > > > activity go in & out of one account, since GL > > > already had balances > > > representing the asset values. > > > > > > We uploaded, via Atlas, accumulated depreciation > > > balances thru > > > 12/31/06 - posted the entry with a 12/31/06 date - > > > also using the > > > conversion profile. > > > > > > Our IT department than ran an sql for us to change > > > the assets' > > > profile from Conversion to the profile now used > > for > > > ongoing > > > transactions. > > > > > > The benefit of loading original assets is for > > > reporting accurate > > > results... If you were to only load the net book > > > value, usually in > > > accounting, the original cost is recorded in one > > > account, and the > > > accumulated depreciation in another, it would be > > > difficult to > > > reconcile. > > > > > > Hope this helps! > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --- In Axapta-Knowledge-Village@yahoogroups.com, > > > "KamaRaju Vudata" > > > <kamaraju_vudata@> wrote: > > > > > > > > Hi, > > > > > > > > > > > > > > > > I am also having the same issue. Can anyone help > > > me asap as my > > > > implementation date is nearing. > > > > > > > > > > > > > > > > > > > > > > > > Thanks in advance > > > > > > > > > > > > > > > > _____ > > > > > > > > From: Axapta-Knowledge-Village@yahoogroups.com > > > > > > [mailto:[EMAIL PROTECTED] > > > On Behalf Of G > > > > Radhakrishnan > > > > Sent: Monday, July 30, 2007 5:09 PM > > > > To: Axapta Group > > > > Subject: [Axapta-Knowledge-Village] Fixed Asset > > - > > > Acquistion > > > > > > > > > > > > > > > > Hi Gurus, > > > === message truncated === > > > > > _____________________________________________________________________ _______________ > Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. > http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow >
