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.

Similar Messages

  • 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

  • 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

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

  • 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

  • Fiscal year variant Z1 is not maintained for calendar year 2012

    I am getting this error while scheduling infopackage for 2lis_02_HDR.
    Fiscal year variant Z1 is not maintained for calendar year 2012
    PLease let me know how to solve thhe issue.
    Thanks,
    harika.

    Hi,
    Where are you geting error, before execution or duing execution of DTP in the log.
    Check if you have transferred fiscal year variants from source system to BW. Then trigger DTP.
    Regards,
    Pravin Karkhanis.
    Edited by: Pravin Karkhanis on Oct 18, 2011 4:15 AM
    Edited by: Pravin Karkhanis on Oct 18, 2011 4:15 AM

  • Fiscal year variant Z1 is not maintained for calendar year 2012 when loadin

    Dear Experts,
    We are working on BI7.0 extracting data from ECC 6.0.
    I am trying to load data from 0HR_PY_PP_1 which is a Self DataSource in our BW System (extracts data from 0EMPLOYEE and 0PERSON) to load into ZPA_C50 which is a copy of BCT InfoCube 0PAPA_C02 (Headcount).
    The data has come through into the PSA very well.
    However, DTP is throwing an error while loading 32242 records of data from PSA into ZPA_C50 InfoCube. The error details as below:
    Error while updating to target ZPA_C50 (type INFOCUBE)
    Fiscal year variant Z1 is not maintained for calendar year 2012     FGV     2
    Messages for 1 data records saved; request is red acc. to configuration
    Processing Terminated
    We are actually doing a Re-implementation of BW 3.0b in BI 7.0 Ehp1. We have imported Maintenance of Fiscal Year Variant from the BW 3.0b Production System. So this shouldn't be a problem I guess since I have also checked the setting in SPRO in BI 7.0 Development (New) System and they are looking good.
    Also, when I do a Filter on 0CALDAY in DTP from 01.01.1900 to 31.12.2010, the loads are working fine. I want the load to run without any Filters on 0CALDAY.
    Has anyone been in similar situation. How did you resolve this issue? Your time is very much appreciated.
    Thanks in advance.
    Chandu

    Dear Experts
    Thanks for your time.
    We have resolved this issue ourselves. We have maintained 'Shortened Fiscal Years' for 'Z1' and it is working fine now. Steps are as below:
    In BI Dev System -> SPRO -> SAP Reference IMG -> SAP Customizing Implementation Guide -> SAP NetWeaver -> Business Intelligence -> General BI Settings -> Maintain fiscal year variant -> Select 'Z1' Fiscal Year Variant and then DoubleClick on 'Shortened Fiscal Years' to set the Fisc Year Variant -> Save.
    The dataload should work fine now.
    Cheers,
    Chandu

  • Fiscal year not defined for in Year

    Dear All
    I am trying BDC to record hiring action through PA40 for the purpose of mass hiring. While hiring process at 'Create Car & Conveyance allowance' screen a warning message appears "No automatic updation for pernr 12345 .Allowance grpg not found." I skipped it, then another error comes at  'Create Income From Other Sources' screen, that is "Fiscal year not defined for  in Year". In the description of this error I find 'Fiscal year not defined for  in Year'. I checked PA03 also, but I didn't find any clue there.
    Kindly enable me with your expert suggestions to go ahead.
    Best Regards,
    Anand Singh
    SAP HR Consultant

    HI,
    1. Allowance Grouping
    - Check the hiring date and Infotype 8 date.
    2. Income from other sources
    - Check the control record .
    Is it released for the year for which u r entering the data.
    Regards,
    Param

  • Splitting is not working for fiscal year 2008

    hai experts,
    The splitting is not working for fiscal year 2008. This is critical for month end.
    pls explain me ful cycle and advise me what i have to do,
    thank you

    Hi
    Please check the documentation in the links below.
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/1c/2ed140ed61712ae10000000a155106/content.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/87/3da04028f40160e10000000a1550b0/content.htm
    This gives yuo a brief on Document splitting. Please let me know if you need any further help. Please do award points if found useful.
    Karthik

  • Job gets cancelled - Plan version cannot be planned for fiscal year

    hello,
    In R/3, I am trying to delete data using KEPM TCODEand the job gets cancelled with message "Plan version cannot be planned for fiscal year".
    Does anyone know what I should do to resolve it.
    thanks,
    Bhat

    Hello,
    Thanks for your response.
    I have checked OKEQ and
    we have entries for fiscal year planning version and in operating concern the version is locked. I don't know if I should unlock the version and what will be the impact.
    thanks,
    Bhat

  • Delta Fail - Fiscal year variant FP is not maintained for fiscal year 2011

    Afternoon all,
    One of our overnight deltas failed with the error msg
    "Fiscal year variant FP is not maintained for calendar year 2011"
    I've since in SPRO under Maintain fiscal year variant created the correct entry for 2011 which mirrors the R3 source system. However when i run a repeat delta the same error occurs.
    Thinking i may have missed a setting i have since transferred the global settings for fiscal year variants from the source system in RSA1 and again ran a repeat delta...same error.
    On the advice from other threads in the forums i've checked in OB29 and it appears fine, and also checked tables T009 and T009b again without success.
    Does anyone know of anything else i can try?

    hi,
    hope run the delta after the attribute change run could solve the issue.
    hope u may have the below posts already if not chk out
    Fiscal variant maintence
    Maintaining Fiscal Variant Between R3 and BW
    Fiscal variant not maintained for Calender year
    Ramesh

  • SAP EXIT Variable 0FYEAR is not working for Fiscal Year(OFISCYEAR)

    Dear SDN,
    I have created Simple Query.
    ROWS
    Company code(0COMP_CODE)
    Fiscal Year(0FISCYEAR)
    Columns
    Total Debit postings(0DEBIT)
    Total Credit posting(0CREDIT)
    Filters
    Companycode(Variable Selection option)
    Fiscal year(Varialbe SAPEXIT 0FYEAR)
    Fiscal Year Variant(K4)
    After executing the query in the variable screen only company code is displayed.
    SAP EXIT FISCAL YEAR VARIALBE(0FYEAR) IS NOT WORKING.....
    Is there any setting or activation is required to use SAP EXITS?
    Waiting for Solution......
    Thanks & Regards,
    Praveen.K

    Hi
    In this case you will have to use a Customer Exit (which is Ready for Input) Variable which gets Current Fiscal Year as a Default Value.
    In order to do that - you will need to create a Customer Exit Variable which is Ready for Input. The Variable will have to be assigned with Current Fiscal Year under I_STEP 1 (this refers to the coding of the Customer Exit in T-code: CMOD)
    If you need any help with the coding - don't hesitate to ask.
    Yaniv

  • Offset not working for fiscal year variable 0P_FYEAR

    Hello all,
    I am working in G/L cube. I am getting total credit and total debit keyfigures from the cube.
    I want values for 2 years side by side. So I am using 0P_FYEAR as varaible for the key figure and offsetting the other by -1 but for some reason the offset is not working. ?
    If I run the query just for 2007 is get the values, if i run just for 2006 I see the values for but when I use the varaible and input the fiscal year as 2007 in varaible screen than I see the values only for 2007 and not for 2006 ?
    The test data in cube is for 2006 and 2007
    Why can that be ?
    Any suggestions?

    Hi KM
    Thanks for your prompt reply.
    I created another simple query with 2 RKF's, one RKF uses the user entered value ( 0) and onther RKF is offset to -1 and it is very straight forward query.
    The second RKF query result came blank. Infact i tried with my own variable which i have created not SAP variable, but still no luck.
    Do you have any thoughts.
    Thanks for all your help.
    Prasad

  • Country Grouping does not exist for tax year 2012 01

    I get this error when simulating payroll for period 01 in tax year 2012. I use the South African payroll.

    Would that be because payroll period does not exist?
    You can use the report RPUCTP00 (Generate Payroll Periods) Check this out:
    [http://help.sap.com/saphelp_45b/helpdata/en/35/a47c3c763e0392e10000009b38f9b7/content.htm]
    Otherwise, please specify more, message class, where it occurs in payroll process... etc..
    Hope it helps.
    Regads,

  • SAP BW DTP error: Fiscal year variant is not maintained for calendar year

    Hi experts,
    Running DTP for loading 2LIS_12_VCITM results in following error "Fiscal year variant A2 is not maintained for calendar year 2012".
    I have already done following checks:
    - the fiscal variant A2 exists for the fiscal year 2012 in the BW system (T009 tables)
    - the DTP does only give this error for 2 company codes, and works fine for other company codes
    - in our R3 system, the fiscal year variant A2 is assigned to all the company codes, how or where can I check this assignment in the BW system ?
    Kind regards, Guy Verschueren

    Hi
    Please check the following threads
    "Fiscal year variant V3 is not maintained for calendar year 2011" (OAOB)
    Error FGV002: Fiscal year variant & is not maintained for calendar year &
    Hope it helps.
    Thanks,
    Rajesh.
    Please assign points to answers if you find them heplful

Maybe you are looking for