Error is due to depre periods

Hi All,
During depreciation run, the following error shows:
Maximum investment amount exceded in area 51
Message no.AA642
Asset affected :  00000000000xxxxx-000000
Diagnosis
Process terminated, because the total investment support amount 1234.00 exceeeds the maximum amount 1233.00 in area XX (deprectiation area).
Procedure
Either correct your entry or change the maximum amount limit in Customizing.
Please adivise how to recitify this.
regards
ss

Hi,
Hope you have maintained a minimum Asset Value as Rs.1,
Please check the same in Memo Value in the following places,
1. Memo Value as per Asset Class - OAAW,
2. Memo Value as per company code in which Depreciation Area - 51 - OAAI.
Hope this will help you,
regards
N.Kumar

Similar Messages

  • Fi posting error due to fiscal period error 1

    HI SAP GURUS,
    I am trying to post TR6 Challan in todays date & getting following message-
    Fi posting error due to fiscal period error 1
    Message no. 8I216
    Diagnosis
    Attempt to post the document in a period outside the current Fiscal
    period  setup.
    Procedure
    Change the posting date  or  Change the fiscal  period prior to posting
    the  transaction under consideration.
    please help me to resolve the issue.
    CHEERS

    HI
    This error is due to Posting period is not open in FI check the posting period is opened for all the accounts in OB52 then post the entries
    hope it will be usefull

  • Problem with posting vendor invoice (MRHR) due to posting period

    Hello,
    Good day.
    Recently, due to the closing of posting period 12 2006, a new posting period was created for 2006 to reconcile some unproccessed posting for that year. This posting period 13 2006 was created in FI (OB52).
    Unfortunatley, even though posting period 13 2006 is available. When creating a vendor invoice (MRHR) with reference to PO, specifying the posting perio 13 2006 would create an error message
    <b>"Allowed posting periods: 01 2007 / 12 2006 / 12 2006"</b>
    I debuged the program and tracked down the source in the table MARV, which seesm to be maintained in the transaction code OMSY.
    However, when I tried to change the data for the company code a message would apperar
    <b>"The company code <ccode> can no longer be initialized"</b>
    I also tried tcode MMRV and allowed posting to previous period, but that didnt work.
    What actions do you guys suggest so that the Vendor Invoice/Invoice Verification can be posted in period 13? Thanks and good day.

    Thanks very much, i'll check it when my internet is stable. Unfortunatley the earthquake in Taiwan messed up our internet
    Award points once I see it!
    If there are any other tips that may prove useful please feel free to post them.

  • Error 0x80070079: The semaphore timeout period has expired

    Whenever I try to copy large files over a wireless network (Laptop > Desktop) I get the following error:-
    Error 0x80070079: The semaphore timeout period has expired
    I've done a search on Google and have found that a number of other users are having the same problem, but no-one seems to have a fix for it.
    Can anyone help?
    (I'm running Vista Ultimate on both my Laptop & Desktop)

     Lionel Chen - MSFT wrote:
    Hello Ady,
    Thanks for your post!
    This issue may be a little complex and require some steps to troubleshoot:
    1.    Update the driver of wireless network adapters in both of your computers.
    2.    Temporarily disable all the firewalls and anti-virus applications, then check the issue again.
    3.    To exclude the factors from other services and applications, do a clean boot to check the issue and perform Step 4.
    (KB929135) How to troubleshoot a problem by performing a clean boot in Windows Vista
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;929135
    4.    With clean boot, try to apply the hotfixes contained in the following KB articles:
    (KB932045) Error message when you use a network connection to copy a large file from one Windows Vista-based computer to another Windows Vista-based computer: "The connection has been lost"
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;932045
    (KB932063) Several problems occur on a Windows Vista-based computer when you work in a wireless network environment
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;932063
    If problem still persists after steps above, this issue is very possibly due to network devices or configurations, please let me know:
    1.    Whether this problem occurs in wired network?
    2.    If strengthening the network signals, the problem can be changed?
    3.    What size of files will lead to this error.
    4.    Does this error terminate the copy process?
    5.    Models of the wireless network adapter and wireless router.
    More details about his issue are preferred. Thanks!
    Have a nice weekend!
    Regards,
    Lionel Chen
    Microsoft Online Community Support
    Well this did'nt work for me.
    Any other solution?
    Using XP Prof. Service Pack 3 beta.

  • During PGI - Error - Posting only possible in periods 2006/12 and 2006/11

    Hi,
    I am a new to SAP.
    I am testing creating sales order. While posting Goods Issue,  I am getting error " Posting only possible in periods 2006/12 and 2006/11 in company code 1000"
    I searched and got solutions in SDN- Forum  as well as SAP best practice buidling blocks and tried but still the same error is appearing.
    I tried the following:
    1) Transaction code - OMSY - The details for company code 1000 is:
    Year-Period-Fin Year - Period-Fin Year-LM
    2006-12     -2006       - 11      -2005     -12
    I modify this to Year to 2011- Period to 1-other fields not possible to modify and save, but the changes does not reflect when we open this screen again. It displsys old date.
    2) Then I tried Transaction code - MMPV -
    I enter the follwoing details
    From Company code -1000
    To Comnpany code -1000
    Period
    Year  - I tried to enter from 01/2005 to 12/2010  and click execute, i am getting error mesasage that these are not current year.
    If i enter 01/2011, it is going to next log page but with errror message that 01/2011 is not current year and 12/2006 is current year.
    3) Then  I tried - SPRO - Financial Accounting (NEW) ® Financial Accounting Global Settings (New) ® Ledgers ® Fiscal Year and Posting Periods ® Posting Periods ® Open and Close Posting Periods
    and entered the follwing data and save.
    Var. A    To account    From per. 1    Year    To period   Year    From per. 2    Year    To period    Year
    1000 +                               1                 2000        12         2011     12                   2000     16            2011
    1000 A    zzzzzzzzzz       1                 2000        12         2011     12                   2000     16            2011
    1000 D    zzzzzzzzzz       1                 2000        12         2011     12                   2000     16            2011
    1000 K    zzzzzzzzzz       1                 2000        12         2011     12                   2000     16            2011
    1000 M    zzzzzzzzzz       1                 2000        12         2011     12                   2000     16            2011
    1000 S    zzzzzzzzzz       1                 2000        12         2011     12                   2000     16            2011
    Please suggest how to clear this error message.
    Regards
    Kasi

    Dear Kasi
    its not a problem if you are working on IDES.
    Enter T code SE16N.
    Enter table name MARV. Press enter.
    Enter your company code in the required field. Press enter.
    Enter   &SAP_EDIT   in the place where you entered the T code. Press enter. Now it is in edit mode.
    Execute (click on Clock icon). A new screen appears.
    Enter The Current Year: Current Month: Year of the previous Month: Previous month: Last year: Last month of the calendar year. As asked in the screen.
    Press enter. Save and come outside.
    Please do remember all the time period should be as per your system calendar.
    Also do remember this is only workable when you are using IDES for education purpose only. Because skipping so many periods in between can cause problems when you are on real time scenario. Using MMPV is the standard procedure where you close the periods one by one.
    Try it.
    Update forum.
    Pawan Sharma
    Edited by: Pawan KS on Feb 10, 2011 12:33 PM

  • Cause is mentioned as : "The cause for this error is due to person name is not assigned to the FND_USER."

    Cause is mentioned as : "The cause for this error is due to person name is not assigned to the FND_USER."
    Do we need to attach the person name of employee whose reverse Global deployment we are doing or the person name of the person who is doing this transaction.
    Thanks & Regards,
    Kirti Mohan Sharma

    You just need to attach the person to the FND User. System Administrator responsibility - Security - User screen.
    After you have linked the person, you can check the table
    Select * from FND_USER
    Where user_name = '<user_name>';
    Cheers,
    Vignesh

  • There is a sign screen error, probably due to insufficient memory.

    When I open a pdf (MacOSX 10.8.5) I get this message 'There is a sign screen error, probably due to insufficient memory.' (translation out of Dutch).
    Via Photoshop I can open the file, that's the strange thing about it.
    Someone an idea what the problem is and ofcourse what the solution is.

    The Acrobat forum is here:
    http://forums.adobe.com/community/acrobat
    and the Reader one, here:
    http://forums.adobe.com/community/adobe_reader_forums
    This one is only for discussions on the forums themselves.

  • Error 0x80070079: The semaphore timeout period has elapsed.

    Trying to Copy videos from Windows 8.1 Enterprise Dell Inspiron PC to Seagate Slim drive. I keep getting following error:
    An unexpected error is keeping you from copying the file.If you continue to receive this error, you can use error code to search for help with this problem.
    Error 0x80070079: The semaphore timeout period has elapsed.
    Size 138 MB
    Availability: Available Offline
    Please suggest

    Hi,
    In addition, please also take a look into the below thread:
    Error 0x80070079: The semaphore timeout period has
    expired
    Please take a look at the reasons mentioned by Robinson Zhang, and then check if issue could be solved in safe mode.
    Best regards
    Michael Shao
    TechNet Community Support

  • Error during GI due to posting period

    Hi ,
    I am getting an error during goods issue which says posting period not open.I guess that we have had deliveries that were created and in process while crossing over from one financial period to another quite frequently before, but we were still able to goods issue them in the next period. Can anyone tell me why this error happens and if there is any work around for this?
    Thanks,
    Hari.

    Hi
    Use T.code OMSY to see whether posting periods in MM are open.
    Use MMPI--To initialise posting periods in MM
    Use MMPV--to close posting periods in MM
    Use OB52 to see the open and close Posting periods
    make sure that the FI posting periods are in sync with the MM posting periods.
    Regards
    Aravind
    ASSIGN POINTS IF USEFUL

  • Error on invoice "specify payment period baseline date".

    Hi Experts,
    When I create ZMIRO, ZMIRO it keeps
    asking for a baseline date which we have never had to do before
    Payment terms  filled blank, but teh system throughs error message "specify payment period baseline date".
    I
    Please help.
    Thanks,

    Dear,
    System will want to calculate due for payment to vendor for this invoice it must know baseline date from which it should start calculating the due date. Generally baseline date is determined from payment term but it is empty in your case. Enter a payment term in vendor master so that system will default the baseline date from settings done in payment term.
    Baseline date has to exist in the invoice document.
    Regards,
    Chintan Joshi

  • Enter Valid code,Tax Definition [Message 173-36] error while creating new posting period

    Hi Experts,
    We are not able to create posting period of 2014-15 as we are getting this error.
    Enter Valid code,Tax Definition [Message 173-36] error .Please find the enclosed error screen shot for your reference.
    Regards
    KMJ

    Hello KM Jayaprakash
    I have the same problem, but i dont see (know) the screen which i can check  "Advanced G/L account determination  check box". I am in SAP B1 9.0 PL15. Please can you publish a screen shot.
    it's urgent please.
    Thanks

  • ERROR while MM17 for frecast period change

    Hi,
    While MM17 i am geting error mesage , we have 220 items for which i want to change the Forecsat period  when i excecute MM17 for 115 items i am getting error message as below
    Messages have been issued: number MASS000167000001
    Message no. MK101
    Diagnosis
    During inbound processing for the IDoc, messages have arisen while checking material data.
    System Response
    The system has filed these messages in the form of an application log with the number MASS000167000001.
    Procedure
    View the application log.
    Proceed
    i am not able to understand it what error i s this and how to solve it,    for 105 items it works properly.
    regards,
      zafar

    Do what you are told to do:
    View the application log.
    you can either click the Hyperlink PROCEED in the message detail
    or
    select a message in red  in the message overview and click the button Detail.
    SAP jumps to the detailed messages and you can obtain the message that caused the update error.

  • 'Data Access Error' while trying to delete period using Table Editor in FDM

    Hi,
    I'm trying to delete a period that has been entered wrongly using Tools->Table Editor option.
    But when I try to 'Update Grid' after deleting the Period,I get 'Data Access Error'.
    Could any one let me know how to solve the error.
    Thanks in advance

    Hi Kelly,
    There is no data that is entered in that period.The data will be entered for that period next month.
    POV is also not set to that period,but still the problem persists.
    Thanks

  • Error in AS01 E003 SYST: Period 000 is not valid in financial year variant

    Hello SAP Gurus,
    I am encountering an error when creating an asset for a certain CC. Upon saving, error message 'E003 SYST: Period 000 is not valid in financial year variant' appears which prevents me creating the asset. My FY Variant K4 is already assigned in the correct company code. Not sure if this has something to do in period control, posting period or FY variant.
    Can someone help me explain the root cause of my error?
    Thanks in advance.
    Carlo

    Basically, period control will determine the depreciation start date. For 02, it is Pro rata upto mid-period at period start date.
    This is means that for asset value date after mid month, depreciation will be start from next month.
    As an example,
    asset value date from 01.01.2012 to 15.01.2012  -> Depreciation start date is 01.01.2012
    asset value date from 16.01.2012 to 31.01.2012  -> Depreciaiton start date is 01.02.2012
    etc

  • Unable to cycle error log due to lock that will not clear

    Hello,
    Currently I'm having an issue with cycling the error log on two SQL Server Instances because the file is being used by another process. Simple I know but, when you try to kill the SPID it becomes hung and we are forced to restart the instance, which I want
    to avoid at all costs. To give you some background we use sqldm for our monitoring of the databases and received a message that our Error log reached its max size threshold and to cycle the error log. When I executed exec sp_cycle_errorlog I'm told the following
    message:
    Msg 17049, Level 16, State 1, Procedure sp_cycle_errorlog, Line 9
    Unable to cycle error log file from 'J:\MSSQL10.SQL6\MSSQL\Log\ERRORLOG.1' to 'J:\MSSQL10.SQL6\MSSQL\Log\ERRORLOG.2' due to OS error '32(The process cannot access the file because it is being used by another process.)'. A process outside of SQL Server may be
    preventing SQL Server from reading the files. As a result, errorlog entries may be lost and it may not be possible to view some SQL Server errorlogs. Make sure no other processes have locked the file with write-only access."
    DBCC execution completed. If DBCC printed error messages, contact your system administrator.
    Then I ran the following query in instance A and found that sqldm had a active process.
    SELECT *
    FROM sys.dm_exec_requests a
    OUTER APPLY sys.dm_exec_sql_text(a.sql_handle) b
    WHERE session_id > 50
    and session_id <> @@spid AND( text = 'xp_readerrorlog'  OR  text = 'sp_cycle_errorlog')
    ORDER BY start_time a
    Like I said before when I kill the SPID it became hung and remains in a rollback state (the process is not rolling back). My co-worker had this issue before on this same instance and contacted Idera for support, here was their response "The development
    team provided an update regarding this case. After reviewing the code, SQLdm only reads the SQL logs information in each collection and does not lock this resource. Given the behavior that you described,  this could be a problem of SQL Server 2008"
    I believe they're right because we're only seeing this in these two instances. All other instances using sqldm are not reporting this problem which leads me to believe it is MS SQL Server causing it. This is where I'm stuck and that is trying to find out why
    there is a lock on this file and for what reason. I used Process explorer yesterday to search for any processes that are using ERRORLOG through the Find DLL and Handle window and there were mulitple processes touching this file. When I looked today I'm seeing
    now locks for this file and I still cannot cycle the error log. I ran the slect query above I'm still seeing sqldm SPID in both instances. I'm curious to see if anyone else has had this issue before whether they used sqldm or not. Any information will be helpful
    in tracking this issue down.
    Thank you in advance.
    Process Explorer Search Results
    Instance A
    Instance B

    Hi,
    Generally, I use Process Explorer to find out which process is blocking the SQL Server from cycling the error log file. Open search box for ‘errorlog’ or dentify the entries with Handle or DLL as ‘your error log path’. There could be two
    or more processes relating to that. One of them should be ‘sqlservr.exe’, and the others should be the culprits. Verify the process, and try to terminate it and then you should be able to run the stored procedure ‘sp_cycle_errorlog’ to cycle the
    error log without restarting the SQL Server.
    According to the images, there is no process found. I suggest you start the monitor and launch procexp.exe tool again and see if it makes any difference this time. If still no progress, I think you cannot avoid restating.
    Thanks.
    Tracy Cai
    TechNet Community Support

Maybe you are looking for