Asset Acquisition with Asset Value Date earlier than GI post.date

Dear all,
I am curently using SAP ECC 6.0. We are not creating AuC assets but directly capitalizing assets from investment accounts.
If a material is issued with a date in March and i try to acquire it with asset value date from a previous period, for example in February, the system doesnt issue any message and lets me post the transaction. The accountants claim that this hadnt been possible in the earlier version of SAP 4.6 that we had been using and that the system had issued an error message - "Posting not possible (Value date earlier than capitalization date)"
The accounting logic is that you cant capitalize an asset with a date earlier than the date when it has been in use, i.e. in our case it`s the date the material has been issued from the warehouse.
Does someone know what logic does SAP follow in this case - and if i can set a validation control that will check and compare the two dates?
Any opinion would be appreciated
KR
Severina Koleva

We are on ECC 5.0 and we do get that message, but it is a warning.
AA348...
that said, you can setup a validation using GGB0 and asset accounting

Similar Messages

  • Schedule run issue: Late dates earlier than start/finish dates

    Hi,
    I am running into an issue with one of my contractors. When the contractor sends the xer file, all the critical late start dates are a day earlier than the start date i.e. if the start date is Mar 03, 2011 then the late start date is Mar 02, 2011. I am able to fix it at my end when I run the schedule but the contractor is not. Is there some feature in the global setting that the contractor has to fix in his end to resolve this issue? Any help or advice would be great.
    Thanks.

    Marc,
    When Project was first released there were only two basic start field, Start and Actual Start (in addition of course to the Baseline Start field and a few others). With the release of Project 2010, a manual scheduling mode was introduced. That's when things
    got a little more confusing. Instead of leaving the Start date as is, the Start field was converted to a text field and the old Start field was renamed as Scheduled Start. When in auto-schedule mode, both Start and Scheduled Start are exactly the same.
    Now to answer your questions. To keep it simple, let's assume you are using auto-scheduling.
    1. In order to keep the schedule dynamics intact, it is necessary to update the Start field to agree with what really happened, namely with the Actual Start date. If you do not enter anything into the Actual Start field, Project automatically assumes the
    task started as scheduled, on the Start date.
    2, Yes, Project does its scheduling based on the current plan which is represented by start, finish and other data. Once the project starts, that current plan must be updated so the actual date values come into play. As noted in the lead in paragraph, Scheduled
    Start and Start are the same for auto-scheduled tasks.
    3. Earned value is based on the actual values and the saved baseline data. The "point in time" you refer to is the timescaled data as of the status date.
    Hopefully, this clear up at least some of your confusion.
    John

  • Error for Project finish date earlier than forecast finish date

    Hi Experts
    I have the dates in Project definition as follows:
    Forecast start (PROJ-SPROG):  31.01.2011
    Forecast finish (PROJ-EPROG): 31.03.2011
    If i enter date 30.03.2011 as Finish date (PROJ-PLSEZ), below error message appears: "Finish date is earlier than start date. CJ563"
    The date i have entered is later than PROJ-SPROG, still not accepting.
    It accepts entry of date beyond the date in field PROJ-EPROG.
    Can anybody share thoughts on this?
    Warm regards
    ramSiva

    Can you kindly verify the other sets of dates being maintained in your activity (i.e. earliest & latest)? Are you using default configurations for PS i.e. confirmation dates are checked against basic dates and not forecast dates?
    Regards,
    Syed Ammar Zaheer

  • Why do my recurring tasks have a due date earlier than the reminder date?

    When I create a recurring task in the reminders app, it stores it as a due date 1 day sooner than the reminder date.  Thus, if I set a weekly task for Saturday, it shows up in my date view as being on Friday.  When I look at the details of the task, it shows that the due date was Friday and the reminder date was Saturday.  I know I set it up correctly (for being on Saturdays only) but it's being stored wrong.
    This is happening only for the recurring tasks.  My single-use tasks are working fine.  Has this happened to anyone else?

    Caetano,
    Thanks for the response! The only code it looks like I am getting is Exception Code 30 "Plan process according to schedule.
    When you said that Forward Scheduling did not look like it had been executed which is what I thought. It got me thinking some more.
    I ended up going to Tcode OPPR and checking Start in Past and there the system is set up to be "Control at plant leve"
    Then I went to Tcode OMIT and the Start in Past check box was not marked.
    So I would say we don't have Forward Scheduling set up at my location.
    I am going to work on getting that changed and then rerun MRP to see if our release dates get brought in.
    Thanks again for your help.
    Ken

  • Basic finish date earlier than basic start date while backward scheduling

    I am encountering an issue where in when I am selecting backward scheduling for a process order and I am entering the Basic finish date, afte which system is giving me a Basic startdate which is after the basic finish date.
    For eg:- When i give the basic finish date as 08.12.2011, system is giving me basic start date as 09.12.2011
    I have checked the recipe of the material. In the recipe one major flaw that i found out was that all the activity timings were maintained as 0. But when i created a similar scenario in the testing client, i am not getting the issue.
    Please help.

    Hi,
    Check what is maintawined in number of days the start day is allowed to be in the past in scheduling parameters of the order type, in OPU3. If there is an opening float defined in schedule margin key of the order, and concerning this float backward scheduling finds a start date which falls into past, lead time scheduling will automatically switch to forward scheduling starting from today. 9.12.2011 could have been deducted this way. Also check the factory calendar if days upto 9.12.2011 are defined as working days.
    Regards.

  • Posting not possible (Value date earlier than capitalization date)

    Hello , we are getting the error shown below. I'am not sure where to go to fix this can any offer any advice.
    Thank you
    Posting not possible (Value date earlier than capitalization date)
    Message no. AA 322
    Diagnosis
    Asset 000000040048 0000 was first capitalized on 20080831.
    You cannot post to an asset that was not yet capitalized.
    Procedure
    You have the following options:
    Change the asset value date of your posting.
    Capitalize the asset by posting an acquisition.

    Generally this message will come , if you have created a asset  with a capitalization date say   31/08/2008 and you are settling a Internal order for last period say 07 on with a posting date earlier than capitalization date , say 15/08/2008.
    The System will not allow you to post because the value date cannot be earlier than capitalization date.
    Change the value date to later than capitalization date and post.

  • Can't get access in Time Machine to certain folders for any date earlier than current date/time.

    Can't get access in Time Machine to certain folders for any date earlier than current date/time, even when entering as Admin. Why do certain folders have small red "-" badge in lower right corner of folder icon?  Here's a picture of the dilemma:
    I've tried monkeying with priveleges using Command I, and changing users, but to no avail.  Can anyone help?

    Right.  Here's what the permissions look like from the Finder Command I:
    I'm not sure what "Custom" means, but when I then try to change it to "Read & Write", it doesn't take.... just comes back as Custom. Interesting to note that not only am I logged into Joan's account where the data folder and file lives) to do this, but when I do it from my own account  as Admin (dunc...mpster) I get the same result.

  • Can GR date earlier than GI date?

    Hi,
    Good morning! I have a inquiry want to ask all the MM expert.
    I have a Good Issues date is on 22 May, but the Good Receive date is on 1st May.
    Is this flow acceptable?
    Good receive come before good issues sound not logical right ? But my user able to do that, when I try to reverse back the GR with wrong date, it come out this warning "document flow for delivey cannot be updated.."
    Is that my logic was wrong? Please guide.
    Thank you very much.
    Warm regards,
    PC

    Hello Peai ,
    The will accept the posting dates which may sound illogical .. eg GI date is earlier that GR date for a procured material .
    The system has the following logic :-
    If there is sufficient stock coverage at the time ( system time ) of  posting the document , the system will allow the posting in any date withing the same period . However if the period changes ( i.e , posting date is in the previous period ) then the system throws an error.
    Eg .
    GR thro Po done on 22nd May
    GI for the same done on 1st May
    Logically speaking ... the GI date cannot be earlier than the GR date , but the system allows this as these are in the same period .
    Regards
    Anis

  • Error In Backdated Reservation Creation  Base date earlier than current dat

    Dear Experts,
    Error while creating Reservation for back date.
    Base date earlier than Current date.
    Can we create backdated reservation ? and post goods issue to the same ?
    if it need configuration please explain the steps for allowing creation of backdated reservations.
    Thanks in Advance

    What is the error message nos.?

  • Exit or BAdi for Validating GR posting date Greater than PO creation date.

    Hi all ,
    Is there any Exit or BAdi for restricting users to post GR date greater than PO creation date.
    Regards
    Gibi Philip

    Gibi,
    check this:
    MB_CIN_LMBMBU04                         posting of gr
    Amit.

  • GR date lesser than the PO date, the system should show an error message.

    Dear Gurus,
                         if anybody puts GR date lesser than the PO date, system should display error this happens because the system allows back dated posting of 101 MVT in MIGO.Similarly the IR date should not be less than the GR date. This happens because the system allows back dated posting of MIRO also.
    Regards
    ASHOK K

    Hi,
    Use the badi MB_DOCUMENT_BADI  and compare dates of EKKO-BEDAT and MKPF-BLDAT for MIGO.
    USe the badi IF_EX_MRM_INVOICE_UPDATE PROCESS_AT_ and compare the dates of MKPF-BLDAT and RBKP-BLDAT while saving the invoice for checking the back dated entries and throw an error message.
    Regards,
    Bharat

  • SVC Contract start date different than Product Shipped date

    Hi
    "SVC Contract start date different than Product Shipped date"
    Why this is an issue, what could be the reason, how can I fix this ?
    Appreciate your input.
    thanks
    s

    Hi Siva
    Can you give more details about what you are trying when you see this message? What is the apps version? Are you creating contract from OM or from service contract module? At which stage are you getting this message / error?
    Thanks
    Sid.

  • What's the need for capitalization date and 1st acq. posting date?

    hi guys,
    i was wondering what the system would do with capitalization date and first acquisition posting date ??
    and what will be the problem if i entered an asset value date (in the acquisition transaction) that's earlier than the capitalization date entered in the asset master record ?!

    In practice all assets are not put to use right from the date of purchase.Hence the concept of different dates arises.  One being the acquisition date and the other Capitalization date.
    I would buy an asset today but start using it from a later date.  Depreciation has to be calculated from the date of capitalization and not acquisition. But still for record purpose date of purchase would be important.  Hence both the dates are maintained.
    Hope this has clarified your doubts.
    Thanks
    GU

  • How to GRN date (MIGO) and Goods posting date (MB1C) as a Characteristcs

    Dear All,
    Our customer wants to include GRN date (MIGO) and Goods posting date (MB1C) as a Characteristic for a batch.
    And he wants the system to pick up these dates automatically for batch.
    So in batches will be sorted out based on GRN (MIGO) or Goods posting (MB1C) date.
    Is there any standard characteristics available for these fields?
    How to achieve this functionality.
    Regards,
    Mullairaja
    Edited by: MullaiRaja on Jan 7, 2011 8:28 AM

    Closed

  • Asset report - with asset G/L accounts connected for gross value and amorti

    Hello dear all,
    Is there a way to obtain asset report by asset (and not by asset class) with the G/L accounts connected for gross value (acquisition) and amortization (depreciation) ?
    Thanks
    Edited by: Tarek AYACHI on Jun 1, 2010 10:25 AM

    Look to the report S_ALR_87011990 - Asset History Sheet  for more information about this report look in the wiki part from this forum
    http://wiki.sdn.sap.com/wiki/display/ERPFI/Asset+Reporting
    perhaps you can find with the ransaction ARQ0 - Ad Hoc Reports  you need

Maybe you are looking for