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

Similar Messages

Error: "posting period is not defined for fiscal year variant" in FBICS3

Hi,
I got error "posting period is not defined for fiscal year variant" when I execute t code FBICS3.
I checked in OB29 & t code FBIC010 & noted that the fiscal year variant had ben maintained.
Please advice.

HI,
It was noted that the mentioned t code had been maintain but below mentioned error appear:
Posting period is not defined for fiscal year variant
Message no. GU506
Diagnosis
You have tried to determine a posting date in fiscal year variant for period , fiscal year , but this period is not defined for the variant.
Procedure
You maintain fiscal year variants in table T009.
It was referring to t code OB29. I have checked the detail, in OB29 also details maintain.
Please advice why the error still prompt.

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

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

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!!

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

Version 0 is not defined for fiscal year 2012.

Hello Experts,
While am tring to release a work order, i am getting the below error.
Version 0 is not defined for fiscal year 2012.
Message no. GP626
Diagnosis
The version 0 is not defined in controlling area DE06 for the fiscal year 2012.
You have to maintain the fiscal year-dependent version parameters for all actual versions for which multiple valuation is updated.
System Response
The version 0 cannot be used for fiscal year 2012.
Procedure
Maintain the fiscal year-dependent version parameters for the version 0.
Execute function
By this what i understood is we need to change the Settings for each fiscal year for the version 0 in controlling area DE06.
i.e. we need to add the fiscal year 2012 in that.
Is this correct????
If yes what will be the impact of adding 2012 in that screen?
i think its a soft config only.
Please let me know the correct process
Thanks in Advance,
Satya

Version 0 is not defined for fiscal year 2015.
What to do next ? Please help with it.

Version 0 not defined for fiscal year...

Dear Experts..
Im trying to do an hiring action but system says Version 0 not defined for fiscal year...
Could someone tell me wat could be the reason???
Regards
Shanthini

Hi,
Go to SPRO: Controlling - General controlling - Org - Maintain versions
On the right hand side select version 0 then select controlling area settings.
Again select version 0 on the right hand side and select Settings for each fiscal year.
Then maintain the settings for the relevant fiscal year.
Regards,
Dilek

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

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 message: Ship-to party 1111 not defined for sales area 1000 01 50

Hi friends,
I created a new division 50 reference the one available. I maintained all the combination in sales area as far as I know.
When created SO, I got a error message saying " Ship-to party 1111 not defined for sales area 1000 01 50". Message No VP210
Please advise where I missed configuration.
Thanks,
Linda
Edited by: LindaSAP on May 25, 2010 5:40 PM

Hi,
Please check the below links
Ship-to party not defined for sales area
"SHIP TO PARTY NOT DEFINED FOR SALES AREA "
Ship to party is not defined for sales area..
Ship-to party not defined for sales area
Ship-to party 147 not defined for sales area US DS 20
ship to party -sales area error
Regards
Senya

I'm installing PS CS5 Exteneded on my new laptop. I get an error saying the serial number is not valid for this product. Help!

I'm installing PS CS5 Exteneded on my new laptop. I get an error saying the serial number is not valid for this product. Help!

If you purchased it from Adobe, it is registered and that would prove ownership as well as the emaill they sent with the serial number.
https://www.adobe.com/account/my-products-services.html#MyProductsHeader
Sign in with the email and password that you bought it under.
Click on the triangle next to your product and you will see the serial number assigned to you.
You have a valid record and proof of ownership. Try again.
Gene

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

VERSION 0 IS NOT DEFINED FOR FISACL YEAR 2007,

i am learning SAP PP and i hv ides 4.7,
now WHEN SAVING ORDER i.e DURING COST CALCULATION I GET A MESSAGE THAT VERSION 0 IS NOT DEFINED FOR FISACL YEAR 2007,
ON ANALYSING IT LEADS TO T.CODE OKEV BUT HERE SYSTEM DOES NOT PERMIT TO CHANGE THE VERSION, BUT IN ECC 5.0 IT ALLOWS ,
WHAT IS THE PROBLEM, CAN ANY ONE PL. HELP ME,
analysis of error gives following message:
Activation of the indicator is not permitted
Message no. KT253
Diagnosis
You activated an indicator (Plan, Actual, WIP/results analysis or Variance calculation ) in the basic settings for version 1 in controlling area 1000. However, a higher order of settings (general version definition) prevents you from setting this indicator in version 1.
Note
The following should be taken into account when maintaining a version:
In general version definition you decide whether a version is allowed for
     Panning (with the Plan indicator)
     Actual data update (with the Actual indicator)
Note: In Overhead Cost Controlling, actual data is updated in operational version 0.
Actual versions different from 0 are found at present only for delta versions in Activity Based Costing (CO-ABC), and when you work with parallel assesment ( additional versions):
     A data version from results and WIP determination manages (indicator WIP)
     Another version from variance determination manages (indicator Variance)
     A version for exclusive use (field exclusive application)
You must maintain the version basic settings for each controlling area in which you want to update transaction data. General version definition restricts the settings possible for the controlling area:
     If general version definition does not allow plan and/or actual data update for version, this applies to the version in all controlling areas. If plan and/or actual data updating is allowed for a version in general definition, this can be reset for each controlling area separately (unmark the plan or actual indicator).
     Delta versions in ABC may not be used for parallel valuations in the actual; the same goes for versions with exclusive applications. In both cases, the valuation fields may not be maintained.
To set indicators WIP/Results- or Variance-determination the following conditions apply:
     Both indicators may be set only during setup for the controlling area, when they are already established in the higher level general version definition
     If either indicator is already active in the data bank, then the actual indicator may not be subsequently activated
     If the actual indicator is inactive and either of these indicators is active, then the valuations in the corresponding versions and in version "000" must agree
     If the actual indicator is active, then both indicators must be activated
Versions 0 and 1 are used regularly for various purposes by the system, which sets the following limitations/restrictions:
     Version 0 must always be available. It cannot be used exclusively. The plan and actual indicators must always be active.
     The actual indicator may not be activated in version 1.
If these conditions are violated during version maintenance, error messages are issued. There are three types of error message:
1. While maintaining the general version definition, you can only make changes if they do not violate the conditions outlined above.
2. While maintaining the basic settings in the controlling area, the entries must remain consistent with the higher level entries.
3. You want to maintain version 0 or 1. The restrictions outlined above apply.
Use the "Extras" menu option to display the structure of the entries in the complex data object version:
     Select a version and choose Extras -> Version use.
The SAP System shows which controlling areas use this version.
     Select Extras -> Versions in CO area
This displays all versions used in the current controlling area.
The subordinate entries in the hierarchy (settings for each fiscal year, strategic Activity-Based Costing: transactions for a delta versions) will also be shown for both cases.
Procedure
Do not activate the indicator, or change the higher order of settings in the general version definition.

Raj,
What are you trying to change?
To me you are not suppose to make any changes, you need to select the version "0" and then hit "Settings for each Fiscal year" subfolder.... here you copy the settings of 2006 and change the year to 2007. This should resolve the problem.
Regards,
Prasobh

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

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

Similar Messages

Maybe you are looking for