Depreciation planned but not posted.

Hi all,
There is the following case.
In asset explorer there is planned depreciation which is not posted for prior year. I want to erase this planned depreciation (is incorrect) in prior year without affecting G/L. Could you please advise?
If this is to be made with ABSO and specific transaction type, could you please tell me setup of the transaction type?
Best Regards,
Kyriakos

Dear Kyriakos,
is this prior year closed in FI-AA already? If so, how were you able to close this fiscal year? This should be found as error by the fiscal year close report.
If the prior fiscal year is not closed, then you can either change the depreciation key to a non-calculating one (e.g. 0000) or set a shutdown indicator for the complete fiscal year. This should reduce the planned depreciation to zero. No posting or G/L entry is necessary therefor.
If the prior fiscal year should be already closed in FI-AA (still I would be wondering how you did that), you could use the solution provided in [SAP Note 29694|https://service.sap.com/sap/support/notes/29694].
Hope this helps,
Markus

Similar Messages

  • Manual depreciation and Planned but not posted depreciation forwarded

    HI Expert,
    We would like to request for Product Enhancement for Fixed Asset Module due to the inconsistency in the computation for the following:
    u2022     The planned and un-posted depreciation is already considered as confirm transaction when they compute for the accumulated depreciation to be forwarded next year (as well as net book value beg for next year)
    u2022     But as for the no of months (remaining life) u2013 it will only consider the no of posted months when they compute for remaining life of the asset
    The current feature of SAP affecting our enhancement request is as follows
    1) Manual depreciation is currently validates manual depreciation based on Planned depreciation instead of Posted depreciation
    2) Remaining life computation for next year depreciation is based on posted transaction only
    3) When user wants to fully depreciate the asset, we cannot post depreciation based on remaining un-posted depreciation using manual depreciation
    Based on this feature we want to request for the following enhancement
    1) For the remaining un-posted depreciation (especially if the previous year is already close), we should be able to choose which month we want to post the un-posted depreciation
    2) Since the remaining life computation is based on posted depreciation only, 1) the validation and 2) the net book value forwarded next year should also be based on posted depreciation
    We have a sample computation based on current feature VS the suggested computation for SAP. Is there any way for us to import the file here at the forum? We will wait for your advice
    Regards,
    Amy

    Dear Kyriakos,
    is this prior year closed in FI-AA already? If so, how were you able to close this fiscal year? This should be found as error by the fiscal year close report.
    If the prior fiscal year is not closed, then you can either change the depreciation key to a non-calculating one (e.g. 0000) or set a shutdown indicator for the complete fiscal year. This should reduce the planned depreciation to zero. No posting or G/L entry is necessary therefor.
    If the prior fiscal year should be already closed in FI-AA (still I would be wondering how you did that), you could use the solution provided in [SAP Note 29694|https://service.sap.com/sap/support/notes/29694].
    Hope this helps,
    Markus

  • What is the Impact of just parking invoice doc's, but not posting...

    I would like to know the risk/constrain involved with the below process, which may not be a standard practice.
    1. Service Provider maintains Classic SRM/ECC. Customer maintains own ECC.
    2. Shopping cart created in SRM and PO generated in ECC of Service provider.
    3. PO transferred to Customer ECC. Invoice posting, Payment and FI activities are carried out in customer ECC.
    4. Basic Invoice Information is transferred back to Service provider ECC, so this invoice will be shown as follow on document in the shopping cart. It will show only the invoice number and it is only for the informational purpose. There is neither finance activity nor any reporting are made out that system.
    Service provider just want to Park the document and not to post it, so it won't hit the GL account. This eliminates considerable work FI configuration settings.
    Question is whether this unorthodox method of just parking, but not posting will cause any impact/risk, even though no FI activities is carried on that system.

    Hi,
    'the invoice number and it is only for the informational purpose' and 'In future if we are planning to use any reporting from service provider', in this case of cause there will be a problem.
    But, what Service provider going to do with Parked doc? In future if they're going to post it?I mean if they are have accounts payable why they don't post it?

  • Excise Invoices Captured but not posted.

    Hi,
    How can I see the list of all excise invoices that are captured but not posted. Also list of excise invoices that are cancelled.
    Regards
    Ayyallas

    Hi Ayyallas,
    Have you tried transaction J2IUN and using the button "Display pending invoice".
    You might also be able to see this in table J_1IEXCHDR with field STATUS.
    Hope this helps,
    Adam.

  • Sap treasury flow is due before accrual/deferral key date, but not posted

    Hi,
    I run TBB1 - posted business transactions - all transactions posted
    when i run the tbb4 for product type 51a i got the following error
    sap treasury flow is due before accrual/deferral key date, but not posted
    Please see the image

    Hello, Krishna.
    You haven't posted flow types 1150.
    Please go to your transaction, select "Cash flow" tab, Choose layout "106 Posting view", select flow type 1150 (one from your first screenshot above - use flow type and date) and check "Posting status" field - what's inside (please, provide screenshot)?
    NA T2104
    Short Text
    Flow is due before accrual/deferral key date, but not posted
    Diagnosis
    The corresponding flow is due before the accrual/deferral key date, but has not yet been posted; this may result in the incorrect amount of expenses or revenues being displayed in financial accounting.
    System Response
    The flow is treated by the accrual/deferral function as if were already posted, i.e. the related expenses or revenues are accrued/deferred, where appropriate.
    Procedure
    Post the flow to correct the amounts of expenses or revenues shown in financial accounting.

  • Settled but not posted

    Is there any T-code or standard report which can find the list of transaction which are settled, but not posted?
    I tried TPM20, but only those were posted is listed

    please check if you selected only relevant area (-s) for you, e.g. if you need a list of contracts settled but not posted, then mark 'issue no messages' in all non-relevant areas, like in a screenshot attached.
    /Renatas

  • Impact of just parking invoice doc, but not posting???

    I would like to know the risk/constrain involved with the below process, which may not be a standard practice.
    1. Service Provider maintains Classic SRM/ECC. Customer maintains own ECC.
    2. Shopping cart created in SRM and PO generated in ECC of Service provider.
    3. PO transferred to Customer ECC. Invoice posting, Payment and FI activities are carried out in customer ECC.
    4. Basic Invoice Information is transferred back to Service provider ECC, so this invoice will be shown as follow on document in the shopping cart. It will show only the invoice number and it is only for the informational purpose. There is neither finance activity nor any reporting are made out that system.
    Service provider just want to Park the document and not to post it, so it won't hit the GL account. This eliminates considerable work FI configuration settings.
    Question is whether this unorthodox method of just parking, but not posting will cause any impact/risk, even though no FI activities is carried on that system.

    It is not a normal practice and does not fulfill the intent of the park process but as long as you have controls around preventing those parked documents from being posted this should probably work.
    Consider them to be a little akin to delivery accruals that are never matched to an invoice, my thoughts are you might want to HOLD rather than PARK these documents.
    You will also need to consider what your long term housekeeping and archiving strategy will be for these essentially orphaned documents.

  • Planned Dep not posted for retired assets

    Hi ,
    We are running the asset depreication everymonth end, and it was posting without any errors.
    But suddenly we found that some assets which we retired have still not posted the balance depreication and it is still reflecting in Planned Depreication in AW01N for previous months.
    Eg: Asset retired on 29th of a month. Depreciation was not posted for this 29 days. and this balance still lies in planned depreication even after the depreciation run.
    When i try to do a repeat run it gives an error message,
    depreication for Peirod...... already posted.
    As we have already run the depreciation, kindly suggest what best can be done without affecting the depreciation which is posted for other assets which is correct.
    Thanks & Regards
    Sanjay Marathe

    Dear Ramesh,
    Thanks for the update, i have got once more important information on this.
    The problem lies only in one asset.
    When they posted the depreiciation, in the actual run it gave a warning message that
    " The posted depreciation and estimated depreciation are different" .  But as the user was not aware regarding the Rerun and he has posted depreciation for subsequent periods.
    And now it is not allowing to do a rerun for pervious periods.
    Acq date :           9/11/2004
    DOC       :           9/11/2004
    Retirement date : 29/05/2007
    useful life  :          5yrs
    Dep key LINR :     SLM from remaining life to book value zero.
    Depreciation to the day is checked in the Dep Key
    Exp useful life 2 years 161 days as on 31st march 2006
    It was migrated on 1/4/2006 to SAP.
    Points will be awarded.
    Thanks & Regards
    Sanjay Marathe

  • Depreciation planned calculater not as remaining life balance

    Hi SAP Expert,
    Currently, i have an issue on depreciation planned calculate divided by 12 month instead of 2 month remaining life balance.
    Asset Parameters
    Useful Life: 3 / 0
    Expired Useful Life: 2 / 10
    Remaining Life: 0 / 2
    Net book value balance is 59,907 and scarp value is 1. So depreciation will divided by 59,906.
    Now i see the depreciation posted/planned is every month 4,992.17 for 12 months.
    As the asset just left two month life, isn't that depreciation posted/planned will be 29,953 for 2 months?
    I am suspect configure on depreciation key.
    Please advice where to configure calculate depreciation base on remaining life?
    Thanks
    regards,
    ng chong chuan

    Hi  sanjeev and  Giridhar,
    Thanks for your guys helping.
    My depreciation key is set base on below
    Dep/int                    Phase    Base method      Decl-bal method    Period Control   Multilevel method
    Ord.depreciation    1            0011                   001                       005                  001
    Ord.depreciation    1            0017                   001                       003                  003
    Base method                     
    0011                                                  
    Type of depreciation            Ord.Depreciation                                 
    Dep. Method                       Percentage from the useful life             
    Reduce use.life at FY end    Blank                                                 
    Dep.after plnd life end           No                                                     
    Dep below NBValue zero      No                                                     
    Curb                                   No                                                      
    0017
    Type of depreciation             Ord.Depreciation 
    Dep. Method                       Immediate depreciation
    Reduce use.life at FY end    Check
    Dep.after plnd life end           Yes
    Dep below NBValue zero      No                                                     
    Curb                                   No                                                      
    Detail for the asset:
    Acquisition Date        :  29.09.2006
    Capitalization Date    :   29.06.2006
    Useful Life                 :    3 years
    Depreciation Start Date( Depreaciation Areas tab) :  01.06.2006
    But i have seen the first depreciation posted on 30.09.2006 and not 30.06.2006
    Please advice.
    Thanks
    regards,
    ng chong chuan

  • AFAR test run showing the values but not posting in Real run.

    Hi Friends,
    i have an issue with AFAR recalculating the depreclation. The details are as below;
    1. Asset value date is 15.07.2010. but ordinary dep. start date was set as 01.01.2010 manually by the user.
    2. The Period control method 11, the dep. is calculated for entire year for acquisition.
    3. we have already calculated depreciation from period 12 2010 to period 04, 2011.
    4. Now, we have changed ordinary depreciation start date for 5 asset records from 01.01.2010 to 15.07.2010.
    5. Therefore, we recalculated AFAR for these assets for 2010 and test run is showing the values for these 5 asset. The same was expected by the business.
    6. When we execute the real run, it is not posting and no change in asset explorer for period 12, 2010 or in current period. No error message is available in spool / job log.
    We have opened FI periods as well.
    My question is  that why the system calculating the values in test run and if it is calculated in test run, why it is not posting in update run?
    As per the period control method, the depreciation should not recalculated for half year even we change the ordinary dep,start date from 1st Jan to 15th July.
    I  request you to clarify my doubt and help me to understand the error which is stoping the values in update run of AFAR.
    Best Regards,
    Padmaja

    Hi,
    Sorry...it is not worked out. Alternatively, i tried the shift factor with variable depreciation and i achieved the values which appeared in AFAR test run.
    Thanks for the help.
    Regards,
    Padmaja
    Edited by: PadmajaCH on May 19, 2011 3:26 PM

  • FF67 problem, can't change statement date(statement saved but not post)

    I need to change the statement date of a bankstatement. I did not post the statement yet.
    I used a wrong statement date, and I want to change it, but I saved it after booking the second screen(the one with the
    statement items)
    When I look by Manual Bank Statement Overview I see the bankstatement, but it has no Posting complete remark yet, because it has not been postefdofcourse.
    The problem is I can't change the statement date, because when I try to Post then the systems gives an error because it does not accept the new statement date I want to use.
    Is there a way to solve this problem? The statement has not been posted yet, so I suprised I can't change the statement date.
    Anyway I hope somebody can help me out.

    I had to post them first because otherwise it looks I could not delete the statement.
    I saw no Id with only saving, that's why I post them. then the statement got an id.
    What do I have to choose to make it possible to delete statements, not posted yet.
    I guess I have to select something else because I did not see any Id to choose.
    I do a manual input of the bankstatements (no import).
    Whst's the best I can do now?  What do you mean with FI?
    I guess I can do a manual booking on the three(send/receive and general) bankaccounts to get the right position of the accounts?
    The bankstatements are ok(booked with ff67) only the three accounts I mention above have the wrong position.

  • Success but not Posted Process Scheduler

    Hi all,
    I just installed HCM 9.1 PT8.52, Demo DB, Oracle 11g Database and Windows server 2008.
    I installed and configured the process scheduler (followed the steps) and created a windows service for it, that is 'Automatically started'.
    When trying to run a process scheduler, I'm getting a run status 'Success' but the 'Distribution Status' is 'Not Posted'.
    I suppose it is not finding the location or something?
    What should I check?
    Thanks.
    Bechara

    Thank you!
    The ReportDistAdmin role was missing so I added it.
    I shut down process scheduler and re-run it, but I'm still getting 'Not Posted'
    Is there any additional step to do before trying the reports?
    Update
    And the password was missing in the default local node, I added it and it worked!
    Thanks you Hakan!
    Edited by: Bechara IS on Nov 8, 2012 3:39 AM

  • Adding custom dim in planning but not showing up in essbase

    I'm on 11.1.2. When I add a member to a standard planning dimension it ends up in essbase just fine but when I add a new custom dimension no luck, dimension is missing. I thought it might have something to do with the fact that we were running on a eval license of weblogic but we replaced it with a full license and restarted essbase and planning but same outcome.
    I checked the planning repo and verified that dimension does exist in the "dimension" table
    Any thoughts?
    thx

    Hi,
    That is a strange one, if you restart the planning weblogic service I take it the custom dimension is still there when you log into the application?
    If you are on a windows O/S can you do a refresh and then look at the log :- \Hyperion\logs\services\HyS9Planning-sysout.log see if any errors are getting produced.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Could you please help us for asset depreciation postings are not posted

    HI
    can any body help,
    while creating asset  acqistion date 22 january 2010 and  Capitalized date is December 18 2009, but depriciation caliculating from  acqisition date , where is the mistake happen we did not get , please guide me
    thanks
    Ranamka

    Hi
    we did custimization is correct as you said , multilevel level method Validity start is  "from ordinary start data"
    while creating asset  using as01 we maitained depreciation start is  18.12.2009, but it is considering 22.01.2010 which is first acquisition  date
    as under stand , both dates calander year is different  2009,2010 and my fiscal year is calander year , so system automatically considering current fiscal year , becuase 2009 periods already closed
    please let me know where was the mistake
    thanks
    Rananka

  • Mt940 uploaded but not posting

    Hi Experts,
    I have successfully uploaded a MT940 (SAP structured format) using ff_5 but posting is not happening. What could be the reason and how to resolve it?
    Thanks,
    Surajit

    Hi All,
    Thanks for the responses received so far. After importing the MT940, if I go back, I get the following message ---
    "While importing electronic bank statement, the system determ
    that not all external transactions (business transaction cod
    text keys, or posting texts) were in
    table T028G.
    Enter the transactions in table T028G.
    Afterwards, start the processing again.
    Following entries missing in table T028G:
    TransTyp External transaction        +- Bank Key        Bank Account       Shrt key St no MR no
    MT940    /PT                         +  242000          30039501            413788  5745     3
    MT940    /PT                         +  242000          30039501            413788  5745     4
    MT940    /PT                         +  242000          30039501            413788  5745     5
    MT940    /PT                         +  242000          30039501            413788  5745     6
    MT940    /PT                         +  242000          30039501           413788  5745     7
    MT940    /PT                         +  242000          30039501            413788  5745     8
    MT940    /PT                         +  242000          30039501            413788  5745     9
    MT940    /PT                         +  242000          30039501            413788  5745    10
    MT940    /PT                         +  242000          30039501           413788  5745    11
    MT940    /PT                         +  242000          30039501            413788  5745    12
    MT940    /PT                         +  242000          30039501            413788  5745    13
    MT940    /PT                         +  242000          30039501            413788  5745    14
    MT940    /PT                         +  242000          30039501            413788  5745    15
    MT940    /PT                         +  242000          30039501            413788  5745    16
    MT940    /PT                         +  242000          30039501            413788  5745    17
    MT940    /PT                         +  242000          30039501            413788  5745    18
    MT940    /PT                         +  242000          30039501            413788  5745    19
    MT940    /PT                         +  242000          30039501            413788  5745    20
    MT940    /PT                         +  242000          30039501            413788  5745    21
    MT940    /PT                         +  242000          30039501            413788  5745    22
    MT940    /PT                         +  242000          30039501            413788  5745    23
    MT940    /PT                         +  242000          30039501            413788  5745    24
    MT940    /PT                         +  242000          30039501            413788  5745    25
    MT940    /PT                         +  242000          30039501            413788  5745    26
    MT940    /PT                         +  242000          30039501            413788  5745    27
    MT940    /PT                         +  242000          30039501            413788  5745    29
    MT940    /PT                         +  242000          30039501            413788  5745    32
    MT940    /PT                         -  242000          30039501            413788  5745     1
    MT940    /PT                         -  242000          30039501           413788  5745     2
    MT940    /PT                         -  242000          30039501            413788  5745    28
    MT940    /PT                         -  242000          30039501            413788  5745    30
    MT940    /PT                         -  242000          30039501            413788  5745    31

Maybe you are looking for