Create asset-error"E003 SYST: Period 000 is not valid in financial year var

Error during Asset Creation: E003
AS01: Create asset was executed. During saving the asset got an error
E003 SYST: Period 000 is not valid in financial year variant
Following are the Depr keys assigned;
LINA is being used for Book Depreciation
MSTL Depreciation key is being used for ACRES, ALT MIN, ACE, E&P.
Asset Class is Buildings

Hello!
I had the same problem a few month ago. There is a SAP note about this. Run the Asset Year end technical proces in ARJW. Try again your asset creation.
Greetings,
Stéphane

Similar Messages

  • 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

  • FGV003 - SYST: Period 000 is not valid in financial year variant K4

    Hello,
    I am getting the error below when trying to bring Period 000/2008 from our BCS cube into a basic cube.  I've run the "Transfer Global Settings" for our R/3 system but am still getting this error.  The BCS does have Period 000 Yr 2008 with FYV K4 and is showing in the master data for fiscal period.  Any ideas??
    SYST: Period 000 is not valid in financial year variant K4
    Thanks,
    Senthil

    Dear colleagues:
    The same problem is appearing to me. I am trying to run a job in background but the following error appears to me>
    SYST: Period 000 is not valid in financial year variant 36
    Do you know what I have to do to suprime the error?
    The job I am trying to run is for creating an evaluation in order to run the report S ALR 87012167
    Your Sincerely
    Leonardo López
    FI Consultant

  • BEX Error: SYST: Period 053 is not valid in financial year variant M2

    Hi All,
    We have a merchandising report which bring the data for current year and previous year. While I execute the data for Fiscal Year/Period - 011.2011, I get the output. But when I execute the report for Fiscal Year/Period - 012.2011, I receive the below error.
    SYST: Period 053 is not valid in financial year variant M2
    We have variants M4 and M2.
    M4 is month wise where are M2 is weekly.
    In table T009B, we have a record for week 053 for year 2011 whereas we don't have a record for week 053 in year 2010. This is obvious as there are only 52 weeks in 2010 but 53 in 2011.
    I'm not able to track the exact reason for this error.

    Hi All,
    Thanks for the reply.
    I have tried maintaining entry for week 053 against year 2010 in T009B but this didn't work. I checked the 'Check Table' button for any dependencies and I saw T009 table.
    I maintained the entry as below in T009 table and it worked. Can someone explain how this work?
    Earlier entry for which I received the error:
    Fi.Year Variant    Year-dependent     Posting period    Special        Periods Description
    M2                            X                      052                     00              Retail Calendar Weekly
    Changed entry for which the error stopped appearing
    Fi.Year Variant    Year-dependent     Posting period    Special        Periods Description
    M2                            X                      053                     00              Retail Calendar Weekly
    Please help me understand so that if I transport the entry to Production, I don't face any serious issues.
    Regards,
    Murthy

  • Customer Exit Variable Period 000 is not valid in financial year variant Z2

    Hi all,
    I am trying to get the week number from a particular posting period. But I get this error when I execute the Query:
    Error Group
    RFC_ERROR_SYSTEM_FAILURE
    Message
    SYST: Period 000 is not valid in financial year variant Z2
    I checked in "FIRST_DAY_IN_PERIOD_GET" FM and it is not accpting period 000 for PERIV Z2. It works fine for all other periods.
    Does anyone have an idea on this?
    Thanks.

    Simon,
    So do you think that there is a problem in my Query restrictions? You ask me to restrict from 0 - 12, but this period is calculated based on the SY_DATUM in a cust. exit variable. And this period is being used to pull week number. So, do I need to change the code?
    But I already have another query which is similar to this, only ready for input options are missing in the new one. The older one is working fine but the I have problem with this.
    Any more ideas?
    Thanks!!

  • SYST Period 012 is not valid in financial year variant R2 Msg no;FGV003

    Hi SAP Gurus,
    I have encountered with an error as following :
    SYST: Period 012 is not valid in financial year variant R2
    Message no. FGV003
    Our client following calendar year till December 2009.  They want to change to April to March , from April 2010 . So we need to define a shortened fiscal year for January to March 2010 for 3 months.
    One important thing is Depreciation should be calculated only for 3 months ie., from January 2010 to March 2010 for year 2010. For year 2011 u2013 April 2010 to March 2011 be calculated.
    I have done the following settings :
    Current fiscal year variant = K4, i.e. the standard variant with 12 periods (calendar year)
    -the current fiscal year must be closed on 31.12.2009
    -this change have to be done in the next month, i.e. on 01.01.2010
    -on 1.1..2010 starts the new fiscal year 2010
    -the fiscal year 2010 ends on 31.03.2010 and have 3 posting periods
    1) Create a new Fiscal Year Variant for the shortened fiscal year u2013 e.g. "R2" (OB29).
    2) R2 to be made Year Dependent. Current Period Configuration
    Month Days Period Year Shift
    1 31 1 0      
    2 28 2 0
    3 31 3 0
    4 30 4 0
    5 31 5 0
    6 30 6 0
    7 31 7 0
    8 31 8 0
    9 30 9 0
    10 31 1 +1
    11 30 2 +1
    12 31 3 +1
    3) Company Code assignment (OB37): K4 to be replaced with R2 .
    4) Controlling Area (OKKP): K4 to be replaced with R2.
    5) Fiscal Year to be shortened for Depreciation Areas in Asset Accounting customization (OAYP).
    6) Table T093C to be viewed to check whether the field XRUMPF (Shortened Fiscal Year) has been activated with u201CXu201D..(SE 11 Check Table) Done manually
    Other Problem : 1. The system calculates deprecation for period 3 ( Full year deprecation) as seen from AW01n for one asset.
    2. When I run AFAB for 2010 period 1 the error is displayed
    SYST: Period 012 is not valid in financial year variant R2
    Message no. FGV003
    Please anybody help me in this issue .
    Subbu

    Have you maintained the Year Shift Properly in OB29
    For e.g if Financial Year is from July to June, year shift will be as follows:
    Month      Days        Period       Year Shift
    1     31     7     0
    2     29     8     0
    3     31     9     0
    4     30     10     0
    5     31     11     0
    6     30     12     0
    7     31     1     +1
    8     31     2     +1
    9     30     3     +1
    10     31     4     +1
    11     30     5     +1
    12     31     6     +1
    Check also FI period and aseet periods are open through OB52 and AJAB

  • SYST: Period 012 is not valid in financial year variant V3 Message no. FGV0

    Hi!
    While I am going to create Asset it is giving me following error :
    SYST: Period 012 is not valid in financial year variant V3
    Message no. FGV003
    I checked in OB29, I have maintained 12 period,
    can you please tell me what will be the problem.
    Rakesh

    Have you maintained the Year Shift Properly in OB29
    For e.g if Financial Year is from July to June, year shift will be as follows:
    Month      Days        Period       Year Shift
    1     31     7     0
    2     29     8     0
    3     31     9     0
    4     30     10     0
    5     31     11     0
    6     30     12     0
    7     31     1     +1
    8     31     2     +1
    9     30     3     +1
    10     31     4     +1
    11     30     5     +1
    12     31     6     +1
    Check also FI period and aseet periods are open through OB52 and AJAB

  • "SYST: Period 012 is not valid in financial year variant Z4"

    Hi
    Iam getting this error  "SYST: Period 012 is not valid in financial year variant Z4"
    in Asset accounting  when using the shortend fiscal yr with 9 periods in 2010.
    Generated the period control OA84 for this variant Z4  but still getting the error.
    Please advise.
    Thanks in advance

    Srini,
    Our FY is Apr 2 march.
    For 2010 , i put below and in shortend fiscal yr tab i put 9. still having this error.
    1     31     10     -1
    2     28     11     -1
    3     31     12     -1
    4     30     1     0
    5     31     2     0
    6     30     3     0
    7     31     4     0
    8     31     5     0
    9     30     6     0
    10     31     7     0
    11     30     8     0
    12     31     9     0
    Please help
    Thanks,
    Heera

  • Period 012 is not valid in financial year variant V3

    Hi all
      i already posted this issue on ASSET ACCOUNTING two weaks ago ....but still waiting for your responce  .............
    Can any one pls help me out ..........its an urgent ...........
    when i check dep. thro' t.code AW01N/AS02 i am getting an error like "SYST: Period 012 is not valid in financial year variant V3".....
    i don't know why the system is throwing this type of error and where i have to do changes...........
    i am in 4.6c and the dep has not been run for long time . i suppose the last time the dep may be in year 2003......
    Can u guide how to rectify his error........ and bring all the assets upto date and run the dep in the SAP system.
    Presently my clients are posting the manual JV's for every Quater.
    Any help in this would be highly appreciated....
    Revert
    Regards
    Praveen

    Hi,
    Posting periods are controlled by two ways.
    one is technical point of view - OB52 (see here are you maintain account type wise or *)
    second is FI-MM point of view go for OMSY. You can see what are current period open for your company code. You can use T.code MMPV- for close the posting periods and MMRV to open or allow the period for posting.
    Hope this is fine, If yes assign points,
    Regards,
    Sankar

  • Error saying 'Posting period 000 is not defined for fiscal year variant K4'

    Hi All,
       When I try to add a new entry in the transaction OB52, I get an error message saying 'Posting period 000 is not defined for fiscal year variant K4'. The entry that I add is,
    Variant           :  0001
    Account Type: +
    From Period    : 1
    Year               : 1995
    To Period        : 12
    Year               : 2010
    From Period2  : 13
    Year               : 2000
    To period2      : 16
    Year               : 2010
    Please let me know what customising needs to be done to solve this issue.
    Thanks a ton.
    Best Regards,
    Jeff

    Hi,
    Hava you checked in OB52 screen, by default 0001 posting period variant will be there for +, A, D, K, S account types.
    If it is already existed in your OB52 screen, you won't create one more record with the same name. You have to edit the existing 0001 posting period with new values.
    Thanks
    Chandra

  • Asset value date and posting date are not in same fiscal year

    Hi,
    Our business user has created an asset under an incorrect asset class, which he is trying to transfer to a new asset whcih was created under correct asset class. However system is restricting user with the error message "Asset value date and posting date are not in same fiscal year". Can you please advise me how we can proceed further with this error.
    Regards,
    Asam.

    Hi,
    To transfer one asset to another asset within a company code can be done through ABUMN only.
    While doing this transfer you have enter the document date, posting date, and value date for the transaction, but all these dates should be in same fiscal year only.
    In your case you must have been entered the dates for asset value date and posting date , and these two dates are in diff financial years.
    Please make sure that both the dates are in same FY.
    Hope this will fix your issue.
    Thanks,
    Srinu

  • Unable to create foreign key: InvalidArgument=Value of '0' is not valid for 'index'. Parameter name: index

    I am running an SQL(CE) script to create a DB. All script commands succeed, but the DB get "broken" after creating the last costaint: after running the script, viewing table properties of Table2 and clicking on "Manage relations" gives the following error: Unable to create foreign key: InvalidArgument=Value of '0' is not valid for 'index'. Parameter name: index. Wondering what does that refer to...
    Here it is the script. Please note that no error is thrown by running the following queries (even from code that passing the queries by hand, one-by-one to sql server management studio).
    CREATE TABLE [table1] (
    [id_rubrica] numeric(18,0) NOT NULL
    , [id_campo] numeric(18,0) NOT NULL
    , [nome] nvarchar(100) NOT NULL
    GO
    ALTER TABLE [table1] ADD PRIMARY KEY ([id_rubrica],[id_campo]);
    GO
    CREATE UNIQUE INDEX [UQ__m_campi] ON [table1] ([id_campo] Asc);
    GO
    CREATE TABLE [table2] (
    [id_campo] numeric(18,0) NOT NULL
    , [valore] nvarchar(4000) NOT NULL
    GO
    ALTER TABLE [table2] ADD PRIMARY KEY ([id_campo],[valore]);
    GO
    ALTER TABLE [table2] ADD CONSTRAINT [campo_valoriFissi] FOREIGN KEY ([id_campo]) REFERENCES [table1]([id_campo]);
    GO
    Sid (MCP - http://www.sugata.eu)

    I know this is kind of old post, but did this realy solved your problem?
    I'm getting this same error message after adding a FK constraint via UI on VS2008 Server Explorer.
    I can add the constraint with no errors, but the constraint is not created on the DataSet wizard (strongly typed datasets on Win CE 6) and when I click "Manage Relations" on the "Table Properties" this error pop out:
    "InvalidArgument=Value or '0' is not valid for 'index'.
    Parameter name: index"
    Even after vreating my table with the relation in SQL the same occurs:
    CREATE TABLE pedidosRastreios (
        idPedidoRastreio INT NOT NULL IDENTITY PRIMARY KEY,
        idPedido INT NOT NULL CONSTRAINT FK_pedidosRastreios_pedidos REFERENCES pedidos(idPedido) ON DELETE CASCADE,
        codigo NVARCHAR(20) NOT NULL

  • Error: Metadata of component EquipmentShipment is not valid!

    Hello all,
    I have created one webdynpro DC -A which has two DCs as used DC- B & C.
    Now everything builds & runs fine on local server. but when I activate DC "A" gives build errors, as it does not get reference for DC -B.
    Here is the error:
    "Error: Metadata of component EquipmentShipment is not valid! "Role "UsedComponent": A minimum of 1 object(s) is required!" "
    This error is only for "B" not "C"
    I tried rebuild, resync, recreate the dependency through public part but no use.
    Could you please help me with this issue?
    Thanks in advance!
    Regards,
    Sarika.

    Hi Sarika,
    Generally these type of errors occur due to broken DCs. Check DC build for 'B'. You may find more accurate information in the build report. I too faced similar issue once then the problem was some of the RFC changes were not imported. Check whether it is also same case for you.
    If it is a  wd-gen error, try to remove wdgen and gen folders for DC-B and build & try.
    Still you have problem, check this [thread |Re: Local DC problems;whether it can help you.
    Regards,
    Siva

  • After moving from Canada to the US, getting a new iPhone 5C, and restoring my backup from iCloud, I can't update my apps. I get an error message that my account is not valid in the Canadian App store and I must change to the US store. How do I do that?

    After moving from Canada to the US, getting a new iPhone 5C, and restoring my backup from iCloud, I can't update my apps. I get an error message that my account is not valid in the Canadian App store and I must change to the US store. How do I do that?

    Change here:
    Settings > iTunes & App Stores > Apple ID: > View Apple ID > Country/Region.
    You must have a verified billing address & be located in the country whose store you are trying to use.

  • FA-retirement-Asset value date and posting date are not in same fisc year

    Hello,
    I would like to post retirement in the new fiscal year but with asset value date in the previous year so that NBV is calculated correctly. It is not possible neither in ABAON nor in ABAVN with any transaction type.
    I always get message 'Asset value date and posting date are not in same fiscal year'.
    Is there any way how to handle this?
    Thank you,
    Jan

    Hi,
    I have tried this but the settings of our Depr keys works in the way. That if you use asset value date in the new month it will calculate depreciation for the whole month.
    This means if I retire with asset value date 31.12.2008 - NBV will be calculated as at 31.12.2008.
    If I retire with asset value date 1.1.2008 - NBV will be calculated as at 31.1.2009.
    Thank you anyway!

Maybe you are looking for