According to posting cycle, you should post period 012 next

Hi gurus,
i have uploaded the master data in the dev client where taking the values and transfer date as 31.12.2007, so i have to run deprecation for the whole year periodically right and iam not able to run the deprecation and the system showing the error, According to posting cycle, you should post period 012 next so can i change any customization
where i have found the OAYC for book deprecation Dep area as 2008 i cannot able to change that directly is there any option to chnage the year and run the dep from the 01 period for the 2008

Period 012- you have referrd here, is it 2007 or 2008? In OAYC, which period is it showing there as last depr period posted?
Regarding the posting of depr, do you want to post the depr in each period as Planned one?
Also, Can you provide the long text of the error message?

Similar Messages

  • Dep Posting..."you should post period 001 next"

    Hi,
    I have a company code in which we are posting depreciation for the first time. I am running period 9 and it gives me the error "According to posting cycle, you should post period 001 next". 
    Anyone know how to directly calcuate for period 9 instead of running for all periods.
    Is there some way...
    thanks,
    JR

    You are not providing enough information.  Did you just do a legacy system takeover and are beginning in production?  Did you do an upgrade?  Are you "playing" in a test/QA environment and want to caught up.  What is it that you are actually doing/trying to accomplish?
    If while executing AFAB you choose an "unplanned" depreciation run the system <b>will post planned depreciation</b> up to the current period.  In production if you went live with FI/GL as of period 01 then you should run depreciation since period 01 up to the current period (one by one).  Remember that asset accounting is a subledger of the GL and should be kept in sync.  However, that may not possible if your FI periods are already closed and the FI folks will not reopen the posting periods in FI for the previous periods.  Keep in mind that a depreciation run posts in the GL therefore the FI period must be open.

  • 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.

  • You cannot post write-ups

    Guru's
    we are getting this error message while posting the write up for a asset which has Accumulated depreciation for the pervious year as well as normal planned depreciation in the current year.
    You cannot post write-ups
    Message no. AA400
    Diagnosis
    According to the transaction type, you have to post to area 01. However, in this area, there is either no accumulated depreciation or the write-up depreciation type(s) are not managed in this area.
    Procedure
    Check the transaction type.
    who can i post the write up for the assets with out this error??? is this error should be interpreted as, due to no accumulated depreciation or write up depreciation is not in the particular asset for current year or previous year???
    kindly help me in this regards.  Thanks in advance.
    With regards
    Satish Karantth k.

    Hi,
    Write-ups are used for correction of depreciation values calculated in
    the past (closed fiscal years). It is not possible to post write-ups to
    assets that have been acquired within the current year. If you attempt
    this, you will receive error AA402. Please review the R/3 Library
    documentation for further information. The documentation describes the
    procedure for write-ups as well as the two situations where write-ups
    can be used.
    A write-up is generally understood to be a later change to the valuation
    of an asset. This change can take different forms, depending on the
    reasons for the change. A write up can only be posted, if there are
    accumulated values on an asset, it means the posting of a write up
    corrects the depreciation from the past.
    For example - The value adjustments (depreciation) that you calculated
    in the past were too high. You must now correct this error using a
    write-up in the current fiscal year. You can only post a write up, if an
    asset has accumulated values.
    But again the write-up functionality is designed to change prior year
    asset not current year acquired ones.
    If manual changes are necessary it may be possible for you to use
    transactions ABMA - Manual depreciation or ABAA - Unplanned depreciation
    to correct the depreciation amount.
    Open the new fisical year and do the write-up from the previous fisical year
    Regrds
    Venkataswamy

  • 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

  • ASKB error - Posting period 012 2009 is not open

    Hi All,
    We are using ECC 6.0 version.
    We have posted an asset acquisition on 31st Dec 2008 in a Local Dep area with posting date 31st Dec 2009. Posting was made only in Local ledger and not in leading ledger.
    It was a mistake from our side and rectified immediately on the same day by reversing the entry and reposted with posting date 31st Dec 2008
    This issue is erroneous as posting period 12 2009 was open at the time of posting and later realized and has been closed.
    Now, We are trying to run ASKB for all the assets in that Co.Code. But, System is blocking the entire log for processing. The Error being u201Cposting period 012 2009 is not openu201D
    We cannot exclude this particular asset for this run and we cannot even open period 012 2009 for security reasons
    Pls advise.
    Thanks,
    Pavan.

    Hi Pawan,
    May be you can try posting with period 12/2009 opened. For security reasons, you can block the period for others and keep it opened only for a particular authorisation group and have the auth. group assigned to only one person who runs the transaction.
    Regards,
    Mike

  • Posting balance is not cleared (period 01/2007 A) - showing as ERROR

    Hi SDN's,
    When am doing simulation for posting, showing error as
    "Posting balance is not cleared (period 01/2007 A)".
    Plz need your valuable suggestions to solve my issue.
    Thanks for your timings,
    Kind regards,
    Saisree.S

    Hi Sai,
    check the amounts for Balance sheet accounts and Expanses account. find the difference for both the accounts. the difference might be some wage type or wage types amount.
    find the wage types and assign the accounts. then your problem will get solved.
    If the difference amoun is net payment you have to maintain the bank account number. then it will get solved.
    Kumar

  • Error Message- you cannot post write up

    HII friends
    I have an issue that our client have posted unplanned depreciation to one asset which is wrong on 31/3/07. now they want to write up the same on the same date. but system is not allowing the same date it is giving error
    YOU CANNOT POST WRITE UP.
    Message details:
    None of the areas to be posted in accordance with the transaction type entered manages one of the depreciation types entered or cumulative values
    Please help its very urgent///
    sejal

    this issue is solved

  • 'You can post in new year only after closing the previous year

    Hello Experts,
    I am also getting same error while executing depreciation run AFAB ''You can post in new year only after closing the previous year''.
    I found one OSS Note 18800 and it is saying solution as below ...
    At the first depreciation posting in the new fiscal year after a shortened fiscal year, the fiscal year variants must, in all cases, still be entered in asset customizing and in FI customizing for the affected company code. If necessary, all periods for the following fiscal year must be maintained with the variant of the shortened fiscal year.
    Up to 2.2D the following correction must also be installed:
    Please carry out the syntax check only in main program SAPLAFAR.
    But in my case there is no shortended fiscal year.
    Can I apply this OSS note correction instructions ?
    Please suggest me.

    Hi
    I don't think so. Moreover that is applicable till 2.2D.
    Moreover depreciation is to be run for all periods you have not run earlier. Please check upto which period dep run has happened. Thereafter close the fiscal years in order thro AJAB.
    S Jayaram

  • VAT should post based on PO date or GR date not based on MIRO posting date

    Hi,
    Based on posting date in Invoice(MIRO) & condition record validity period, VAT is calculated & posting on invoice posting.
    Condition record for VAT condition type with tax code(T9):
    01.01.2011 to 31.01.2011-------> 4%
    01.02.2011 to 28.02.2011------->12%
    01.03.2011 to 31.03.2011------->14.5%
    PO created and GR done on February & invoive done on March and syatem calculated VAT amount perfactly based on validity period maintained in condition recod and invoice posted.
    But requirement is  system should post invoice VAT amount as mentioned in the PO ( based on PO date) or GR date to post during Invoice posting in MIRO
    Regards,
    Biju K

    Hi,
    Any other input?
    Regards,
    Biju K

  • Post goods issue should be done depending on purchase order acknowledgement

    Hi All,
    In vl02n when i click postgood issue, it should check whether purchase order acknowldgement field in me21n is filled then post good issuse should be done.it its not filled post good issue should not be done. for this which badi or userexit i need to use and where do i need to write the code.

    Hello ,
    you can use BADI 'LE_SHP_GOODSMOVEMENT' , this will trigger when you do PGI in VL02N , in that BADI implementation you need to raise/issue Error Message to stop PGI,That Error Should be captured in the Incomplete Log.
    for more details , please ref documentation of that BADI.
    regards
    Prabhu

  • Posting cycle when a database error is raised

    hello
    I have process train application composed of three page, each page is based on an entity
    1) i fill the first page
    2) i fill the second page
    3) i fill the third page and invoke COMMIT
    There is a database trigger Busniess rule on the table of the second entity that raises an error!
    and therefore an exception is thrown
    To fix the business rule error, a value needs to be modified in the first page,
    I assume that the posting sequence has already posted the first entity
    The error occured while posting the second entity, therefore, the second entity is not posted to the database, No rollback is issued by the program because i want to allow the user to go back to the first page and fix the error rahter than filling a page again
    my question is
    now i have three entities in the transaction list of the Application Module
    1) the first entity successfully got posted and now it not dirty
    2) the second entity is rolled back in the database and i do not know what is status is going to be in the Application module transaction object
    3) the third enitity is never reached
    (no rollback is issued by me)
    I handled the error and allowed the user to navigate back to the first page, the user fixes the Business Rule violation and commits again,
    now a new posting cycle will start
    Will the framwork try to post the first entity to the database again, (it is already posted) or it will understand it is already posted and try to update it. it seems it is trying to insert the row again as i am getting PK violation?
    I disabled database triggers and repeated the situation where the business rules are enforced using beforeCommit() and setting the jbo.txn.handleaterpostexc, things worked better, but the same database triggers handle other application and i cannot just disable them

    Hi Dhana,
    I think it's not possible to use alert. But You can use UDF Marketing document and Formatted Search to show the Downpayment Balance. I'll give you query sample to get the Downpayment Balance :
    SELECT Sum(T0.PaidSum) - sum(T0.DpmAppl) FROM ODPI T0 WHERE T0.[CardCode] = $[$4.0.0]
    HTH,
    YunPho

  • BADI exchange rate according to document date instead of posting date

    Hello,
    I am looking for a BADI that will enable us to change the exchange rate according to document date instead of posting date.
    This change is needed for documents of travel expenses.
    I tried to use substitution but it didn't work for documents created in Tcode PRRW.
    Thank you,
    Dan

    Friend,
    Try to use Field exit functionality.
    You can create field exit for Translation date(WWERT). While currency converstion this date only taken as base.
    Technically you can pass Doc.Date(BLDAT) value to Translation date.
    Or in Substituton(GGB1) also for the header "Transaltion date = Docu.Date".
    I hope it serves your purpose.
    Chandu

  • Posting only posisble error in periods 2009/08 and 2009/07 in company code

    Hi Experts,
    When my user do GI for this month he got error as mentioned below,
    Posting only possible error in periods 2009/08 and 2009/07 in company code
    Already i have done it but still am not confident.
    Also this particular corrections i need to do it in Production system
    Please guide which month i need to enter 1st in MMPV,request you to explain step by step.
    Cheers,
    Kumar.S

    Hi,
    Check in T.code: MMRV and see which period is open for ur Co.Code and back posting is allowed or not.
    In MMPV  open period 09 with your company code.
    Note-1: Check Fiscal Period Variant in OBY6..........is it K4.
    Note-2: From FI side check or Now use t.code: OB52 and open the 09, 2009 period in Account Types A, K, D,M, S and specially Account Type u201C+u201D which stands for valid for all accounts type and save. Better consult FICO consultant for OB52 step.
    Regards,
    Biju K

  • Capital Investment Area was posted Depreciations in an incorrect period

    Hi ,
    Capital Investment Area was posted Depreciations in an incorrect period, they skip a period.
    Can you determine if we can reverse those postings so that they can post in the correct period?
    Would appreciate your fastest reply.
    Regards
    Prasad

    All,
    Thanks for your answers, the solution would appear to be that the commitments have been accidentally carried forward into 2010 Fiscal instead of 2009 fiscal.  
    There are no Invoice plans set up on the PO's, thanks for that suggestion though.
    The reversal in KSCF does not work and produces an ST22 error dump on our system.
    SAP note 971411 appears to fix the error so we will implement the note and hopefully be able to reverse out the commitment.
    Thanks to all and if I can assist you FI guys with MM answers I will
    Allen

Maybe you are looking for