Posting period of "Depreciation Posting Run" problem

Hi all,
I was configured my company code with 12 period of nomal fiscal year (defauld fiscal year variant K4). I think Posting period field of Depreciation Posting Run screen (T-code: AFAB) must have 12 posible entries, are 1,2,3,...,11,12. But when I display posible entries of this filed, it only have to posible entries (000-000, 000-365). So that, I can't choose a period to excute real depreciation run.
How to define posible entries 1,2,3,..,11,12 of posting period field of Depreciation posting run screen?
Chinhvh

Hi,
If I have understood your question correctly
When u do F4 in field "Posting Period" in AFAB you get the following screen:
From            To
000               000
000               365
You don't do F4 in that field. Since your Posting Period Variant is K4, just manual input the relevant posting period in the field. i.e if you want to post depreciation for April then just input Period 4 in the field.
Now what you have to be careful is which depreciation method you are going to select for doing the Posing Run. (i.e the Reason for Posting Run fields)
You have 4 methods which is described below:
1. Planned Posting Run. (This should be done if all the depreciation upto the earlier posting period has been done properly under the planned posting run).
If you have done unplanned run for earlier periods and have never done a planned posting run for the earlier periods for the concerned asset, then you cannot do planned posting run for period 4 directly. You should first do planned posting for period 1, then for period 2, then for period 3, and then finally for period 4. The depreciation will be zero for Posting periods 1,2,3 if your start depn in your asset master is 1st April.
2. Repeat Run: You can use this to do repeat run. You can do Planned depreciation run only once for a particular asset for a particular period. You can then do a repeat run for doing the depreciation run for the same asset.
3.I don't think you wll need to do Restart run.
4. You can do unplanned depreciation run directly for period 4, if you have not done the depreciation run for the particular asset for the earlier period. but this is not recommended. This should be done only in specific circumstances when you have no chance of doing either planned depn run or repeat run.
Pl assign points.
Rgds
PRasad

Similar Messages

  • Depreciation error - Unplanned posting run allow for future period

    Dear ,
    Need urgent advice for depreciation error happen in our production system.
    FYI, our fiscal year variant 2013 = Feb 2012 - Jan 2013 ( We are now at month-end close for Pr 1 2013 ).And fiscal year close 2012 AJAB and Carry forward ARJW have successfully run for new FY 2013.
    In short, in our asset accounting user was accidentally run unplannned depreciation for future period 12/2013 of one particular asset, while we are now in Pr 1/2013. And, Pr12/2013 is open for asset posting.However, no FI posting posted into the system.
    Just a curiosity as to why system allow user to run unplanned depreciation for future posting without giving an error message to follow the posting cycle.
    The impact/error of above unplanned depreciation run:
    User is not allowed to execute AFAB depreciation run for Pr 1/2013. Even worst, in the AFAB program shows from Pr 1/2013 - 12/2013 is already posted when we do depreciation test run. We can't perform any planned,repeat,restart  for Pr1/2013.
    Because of only one asset had accidentally run for Pr12/2013, all of our asset (96,773 asset) cannot proceed with depreciation run for Pr 1/2013 in the new fiscal year.
    This is high priority as it will impact the entire depreciation run for 12 month of our company.
    Your early reply on this issue is greatly appreciated.
    Thank you,
    Regards,
    Latifah

    Thank you for the response.
    FYI, the asset posting actually has been executed but no document was posted as there's no value.
    I've check the 2 tables below:
    ANLC - No numbers of run for any period in FY2013
    ANLP - No depreciation run was posted in FY13 (all periods).
    Is there anyway for us to do normal planned run for Pr 1/2013? As i understand SAP has no function to perform reversal depreciation run in AFAB. How
    With regard to the posting period 12/2013 that is open for user, I already highlighted this to the respective custodian.
    Thanks.

  • Depreciation Run -"Last Posting run terminated Restart in period 03 2010"

    Hello Friends,
    Please help me for this. I am trying to run depreciation for a CoCd 2002 in
    production. When I do AFAB
    for FY 2010 Period 04. It gives a error message "Last Posting run
    terminated, restart in period 2010 003"
    Diagnosis*
    The last posting run in period 003 2010 was terminated by an error.
    Before any more posting runs are performed, you must restart the
    posting run for period 003 2010.
    Procedure
    Start the posting run for period 003 2010 again using the restart
    parameter.
    After this I run AFAB (03 2010) using the Restart radio tab, it runs ok in
    Test and w/o Test (i.e in backgrond),
    when I check SM37 - it shows a program RAPOST2000 is finished. Then I am
    able to run AFAB for (04 2010)
    in test and background also. Again a program is there in SM37.
    But when I try to run for period 05 2010 - it again shows the earlier error
    " "Last Posting run terminated, restart in period 2010 003""
    You see the error message comes again.
    Can someone suggest me a solution. Do I need to go sm35 and process the
    Batch I/P session . Why this error is
    coming up?
    Regards,
    George

    Hi George,
    please look at table-field TABA-XBUKZ.
    If there is a  "1" it means "Restart" necessary.
    If you have the restart sign you have to solve the error and after the restart the TABA-XBUKZ shoudl change to "X".
    regards Bernhard

  • Posting run for future period requested (check entry)

    Hi,
    While taking depreciation run for company code in AFAB system is generating the error message "Posting run for future period requested (check entry)" SAP error AA697
    I checked in OB52 postings periods are open for 2009(all periods)
    SAP note 1150235 (all corrections) and 1153718 are completely implemented.
    Still the problem is not resolved.
    Regards,
    Sankar

    Hi Sankar,
    I would like to refer you to the already implemented note 1153718 which states :
    After you implement the changes, the system issues error message AA 697      
    "Posting run for future period requested (check entry)" immediately when     
    you use a fiscal year that is in the future.  In principle, you can          
    customize this message. However, in this case, no settings are taken         
    into account; the system always issues an error message.                     
    Regards Bernhard

  • AFAB - Depreciation Posting Run Error

    When I tried to execute the Depreciation Posting Run, I get the error message "Internal error with background job scheduling RAPOST2000"
    Hv anyone face this problem before? Pls help!
    Thanks.

    Thanks~ I checked with my colleague, he told me that the user is lost few objects in the role. This included the User Authority and the program objects.
    After he added the objects to the user's role. The issue is settle.
    Thanks~!

  • Can't Run AFAB - Posting run requested for future period

    Hi,
    While taking depreciation run for company code in AFAB system is generating the error message "Posting run for future period requested (check entry)" SAP error AA697
    Diagnosis
    There was a check of your entries in the company code and posting period fields for the current system date. The result of this check is that you requested a posting run for company code xxxx for a future fiscal period.
    Please help me, cause I must close the period.
    Thanks

    Hi
    Check Table TABA, whats your last posted period for depreciation
    If you are executing depreciation for last period + 1, then this error is not justified
    If you are doing it for last period + 2, then its justified
    Br, Ajay M

  • Posting run for future period requested

    Dear Team,
    While taking depreciation run for company code in AFAB system is generating the error message "Posting run for future period requested (check entry)" SAP error AA697
    please help to reslove the issue.
    Regards,
    MAhendra

    Hi,
    look into the Threads,
    Can't Run AFAB - Posting run requested for future period
    Regards
    Andi

  • Posting run request for future period; check your entry message no.AA697

    Hello Guru's,
    I have below error while Depreciation run in T.Code AFAB
    "Posting run requested for future period; check your entry" message no.AA697
    Request help
    thanks in advance
    Regards
    Chintamani

    Hello Chintamani,
    Why you want to post the depreciation for future period?
    Is the future fiscal year in open or is the posting period open for that? If no, please open that period with AJRW T code if you want to post the depreciation for future period but it is not recommendable.
    Check the posting period once again because the given posting period belongs to future year? So please do re-chk and give correct period according to your current fiscal year.
    You can get your fiscal year details and assignment of fiscal year variant to the co,code details in OB29 and OB37 t codes respectfully.
    Check the OSS Note: 1150235 - Preventing depreciation posting run for future
    I hope it helps else revert us with your query.
    Thanks & Regards,
    Lakshmi S

  • Error when run Depreciation Posting Run AFAB

    Hi,
    I found error when run Depreciation Posting Run for period 7 2007.
    FYI. I had run Unplanned Depreciation (TCode: ABAA) with document date 31.10.2007 and posting date 31.10.2007, trans. type 640. After that, i want to run Depreciation Posting Run (TCode: AFAB) with fiscal year: 2008, posting period: 7, reason for posting run: repeat. Select on Test Run. Then i found error message as below. 
    Error Message:
    Documents manually posted within dep.doc.number range
    Message no. AA728
    Diagnosis
    In the number range interval for the document type for posting depreciation, a document  has been posted which was not created within the framework of depreciation posting. The last document posted by depreciation posting was assigned the number .
    Procedure
    Contact your Systems Specialist. When changing the number range interval for the document type in depreciation posting, you have to specify a new interval in which no documents exist. Using organizational measures, you can guarantee that there are no documents apart from those created by depreciation posting in this number range.
    Can any one help how to solve this issue?

    Hi Paul,
    Now I go to TCode: FBN1 - Accounting Document Number Ranges, then i want to change the range for year 2008.
    No Year  From No          To No           Current No          Ext
    03  2001   0300000000   0399999999   -                          /
    03  2002   0300000000   0399999999   -                          /
    03  2003   0300000000   0399999999   -                          /
    03  2004   0300000000   0399999999   -                          /
    03  2005   0300000000   0399999999   -                          /
    03  2006   0300000000   0399999999   -                          /
    03  2007   0300000000   0399999999   -                          /
    03  2008   0300000000   0399999999   -                          /
    03  2009   0300000000   0399999999   -                          /
    Referring back to Asset Accounting, the Reference Document: 19.
    Do it mean that my FI doc. no is 0300000019 ? I bit confuse on this..
    Can you guide me more details on it?
    Thanks in advance.
    Edited by: Nur Aman Abdul Manap on Apr 15, 2009 2:09 AM

  • Is it possible to post the depreciation once the depreciation cycle run?

    HI  ALL
         Is it possible to post the depreciation once the depreciation cycle run?
    IF YES   WHY
    IF NO WHY
    PLZ EXPLAIN ME
    Regards
    raju

    yes we can go for repeat run.But it is possible to repeat the posting run within the period last posted.Normally the repeat run is carried out at the end of the fiscal year, if completing postings are necessary because of corrections to manual depreciation or depreciation terms
    assign points if useful

  • Error AAPO191 in AFAB: depreciation posting run

    Hi,
    I created a new depreciation area and customized the account determination on AO90. When running the AFAB (dep. posting run) the system issues the error AAPO 191 "Internal error in item 0000000000: asset row is not complete"
    I checked the note 859617 which says the accumulated depreciation account must not be set as fixed asset reconciliation account.
    As far as I know, these accounts have to be set as reconciliation accounts otherwise it will be open for manual postings leading to inconsistencies between FI-AA and FI-GL.
    I checked transaction OAMK and it has some accounts in it (but not the ones with errors). Nevertheless, it has no option to include new accounts.
    Can anyone help me out with this error?
    Thanks in advance,
    Paulo Siqueira

    Hi Paulo,
    this error is nearly always about wrong or missing  account control in your account determination. Please check closely     
    note 7595 and verify if any account has been erroneously defined or  is missing.                                                                               
    As per note  7595:                                                                               
    1. Areas to be posted in dialog   > T093-BUHBKT = 1                                                                               
    The balance sheet accounts and the accumulated depreciation accounts must be characterized as reconciliation accounts of account type   'A'. Down payment account KTANZA must also be a reconciliation                                                                               
    2.  Areas to be posted periodically or areas only relevant to  depreciation  -> T093-BUHBKT = 2                                                                               
    Create the accounts of these areas as ordinary G/L accounts.  They may not be reconciliation accounts.   
    Regards Bernhard

  • Depreciation Run Error "Not all the documents in the last posting run were

    Hi,
    When I tried to run depreciation, I found the error message as below.
    "Not all the documents in the last posting run were posted"
    How do I solve the problem?
    Please advise me..
    Thank you for your help..
    Jake

    Hi,
    For an Update termination you need to go into the System Log to check the real cause of the termination.
    My guess is that the document number has already been used. It has happened to me and I found no cause for that.
    I did the following then:
    I checked the highest used document number in that number range and corrected the from number of the number range.
    Then I went into the TABA table and corrected the entries there that they corresponded to the number range.
    Then I did a manual reconcilliation between AA and GL. In my case they matched, If they don't you would need to post manually to the GL to get them to match.
    Then I ran recalculation of asset values. and finally an unplanned depreciation run.
    For me it solved the problem.
    Br
    Cricke

  • Error Depreciation Posting Run

    Dear All,
    I have a trouble about depreciation posting run, there is an error message when I tried AFAB.
    Right now, I already  maintain the validation (OKC7) in order to change the error [E] message become warning only [W], so atleast the depreciation could be posted (depreciation can be posted, althought there is still error on it).
    The trouble already occured for 2 periods (Apr-May), and I've just found the error---there was incorrect posting for the asset class.
    Should I use F-92 (asset retire), ABAON, or there is any other solution for this?
    Please advise...
    Thanks & regards,
    Vanda

    hi,
    try transaction  <b>afar</b>
    (read the documentation of tht report RAAFAR00)
    A.

  • Last posting run terminated (Restart in period 2010 001)

    HI,
    There is the challenge issue for Depreciation run in AFAB,
    While running the depreciation for the month of jan month system never allowing to post.
    After the upload of assets through BDC, this is the first time we are trying to run  the depreciation
    Also, in the test run, some times documents are created and for the same input parameters, if the test run is executed again, the below error appears.
    Job started
    Step 001 started (program RAPOST2000, variant &0000000000027, user ID TRAINING1)
    Last posting run terminated (Restart in period 2010 001)
    Spool request (number 0000010067) created without immediate output
    Job finished
    Can somebody help on this issue...
    Thanks & Regards
    Rajesh Kumar.S
    09620791110

    Hi Rajesh,
    Please check the depreciation (production run) log in AFBP by inputing Company Code Fiscal Year and period. This will provide you mored details of the error as to why the depreciation run went into error.
    After the errors are rectified, please run AFAB in restrat mode, this will resolve your issue.
    Thanks!!!
    Murlidhar Khatri

  • Last posting run terminated (Restart in period 2008 12)

    One Week ago we upgraded from SAP 4.6 to ECC6 and implemented recommendation in note 890976 (in transaction FBN1 I have set the accounting doc. 03 to internal number range determination). The first period (11) we executed the depreciation run for appeared to run successfully but for the second period (12) we are receiving the message "Last posting run terminated (Restart in period 2008 012)". This message will appear each time we run the depreciation for period 12.
    When I run transaction ARMO, I get the error "Document number 2100 300000001 2008 was already assigned
    Message no. F5152"
    In Transaction FBN1, we can no longer set the number range to external and the current status for company 2100 is 300000000.
    Can any one assist with resolving this issue?
    Thanks,
    Nicholas

    Ran some test in our QA system and found the solution. Changed the status number from 30000000 to 30000050 using transaction FBN1. Everything appears to be working now.
    Edited by: Nicholas Archer on Sep 15, 2008 11:56 AM

Maybe you are looking for