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.
Similar Messages
-
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,
JeffHi,
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 -
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,
SatyaVersion 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
ShanthiniHi,
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 -
Depreciation posting rules are not define for area 00 in company code
Dear Expert,
Would like to seek for help, when I run a customize report (AUC without PO not yet capitalized report the system prompt the error depreciation posting rules are not define for area 00 in company code only on the march 2011 on ward but before march 2011 the report is able to display as usual.
Between., does SAP have the standard report to list the asset which is AUC and not yet capitalized?
My version of SAP is ECC 6.0.
Kindly advise.
Regards,
KarenHi,
Thank you for the prompt reply, why the system prompt the error depreciation posting rules are not define for area 00 in company code only on the march 2011 on ward but before march 2011 the report is able to display as usual?
Please help.
Regards,
Karen -
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 ConsultantHI,
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 -
Error : Excise modvat accounts not defined for GRPO transaction and U1 exci
I have Created Impot PO, After Planned Delivery cost MIRO I am trying to Perform GR then its giving Error "Excise modvat accounts not defined for GRPO transaction and U1 excise group
Message no. 8I402"
I have already maintained GL account in "Specify G/L Accounts per Excise Transaction" for Excise group U1
This problem is coming when Additional Duty on custom condition type JADC is maintained in "Maintain Excise Defaults" node in the column "ADC Cond" . If I remove JADC condition type from this place the this error is not coming but AED column is not fetching any value while doing GR.
Please help me in this issue , still No answer
Edited by: shiwanshu singh on Jan 28, 2009 10:26 AMDear sir
For GRPO have you maintained sub transaction Type IP for your excise group U1. If you not maintained pl maintain . and assign G/L account to modvat clearing account , the G/l account should be same as company code CVD account.
Regards
jrp -
ERROR - Excise modvat accounts not defined for CEIV transaction and excise
Hi friends,
I have created excise invoice J1IS- and release to account in J1IV.When I trying to cancel excise invoice in J1IH -> CANCEL excise invoice.ssystem giving error Excise modvat accounts not defined for CEIV transaction and excise I have check account in customization for CEIV and excise group the following accounts are already assign.
CEIV CR Credit MSUSP CENVAT suspense
CEIV DR Debit PLAAED PLA AED account
CEIV DR Debit PLAAT1 PLA AT1 Account
CEIV DR Debit PLABED PLA BED account
CEIV DR Debit PLASED PLA SED account
CEIV DR Debit RG23AED RG 23 AED
CEIV DR Debit RG23AT1 RG 23 AT1
CEIV DR Debit RG23BED RG 23 BED
CEIV DR Debit RG23ECS RG 23 ECS
CEIV DR Debit RG23SED RG 23 SED
where I have to assign modvat account please help me.
Regards,
ChetanDear Chetan
Go to IMG -- Logistics-General --> Tax on Goods Movements --> India --> Account Determination --> Specify G/L Accounts per Excise Transaction.
There, check whether for series group, company code, chart of accounts, you have maintained CEIV. It should have been missing at your end and hence the problem. Maintain the required G/L Account in the above area and retry.
thanks
G. Lakshmipathi -
ARE 1 update error excise modvat account not defined for ARE 1
Hello Expert,
Iu2019m trying to update ARE 1 Document in export scenario, but it shows error -
Excise modvat accounts not defined for ARE1 transaction and K5 excise group
Message no. 8I402
Iu2019ve gone thru Specify G/L Accounts per Excise Transaction in CIN. But exactly in which field we need to maintain the GL.
thanks
GKumarHI,
You are not giving correct Excise inovice no. in J1IH transaction for cancelling. Because if correct excise invoice number is not given then also system give the same error. So please check the excise invoice number carefully
Please check SPRO => Logistic General => Taxes on Goods movement => India => Outgoing Documents => Specify Default Excise Group and Series Group, whether you have assigned the related G/L Account for the given combination with Excise Invoice Type
You will Check following G/L are maintained or not in "Specify G/L account per excise Transaction"
maintain GL account for ETT ARE1 in table J_1IEXCACC for field Mod.Clearing field name is J_1ICLEAR
Cenvat Suspanse G/L
RG23A BED
RG23A ECS
RG23A AT1
Also Check following under "Specify Excise account per excise Transaction"
CEIV CR Credit MSUSP CENVAT suspense account
CEIV DR Debit PLAAED PLA AED account
CEIV DR Debit PLAAT1 PLA AT1 Account
CEIV DR Debit PLABED PLA BED account
CEIV DR Debit PLAECS PLA ECS Account
CEIV DR Debit PLASED PLA SED account
CEIV DR Debit RG23AED RG 23 AED account
CEIV DR Debit RG23AT1 RG 23 AT1 Account
CEIV DR Debit RG23BED RG 23 BED account
CEIV DR Debit RG23ECS RG 23 ECS Account
CEIV DR Debit RG23SED RG 23 SED account
Thanks,
Raviteja
Edited by: Ravi Teja.T on Feb 2, 2012 9:55 AM -
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 -
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 -
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 -
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 youHi
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 -
Error in the source system for fiscal year variant K4 Period 00
We are experiencing the following issue when loading data from module Flexible real estate RE-FX CASHFLOW CUBE OREFX_C06 Error in source system Fiscal year variant K4 is not defined for the period 00.
Hi,
You need to check in your source whether you have maintained Fiscal Yr Variant or not? Talk to you Functional person before you do the BI Extraction.
In Table T009B
You can check Fields
MANDAT - client
PERIV - Fiscal Year Variant
BDATJ - Posting date YYYY
BUMON - Posting date calendar month
Check Table T009B and see if you fiscal variant is maintained for all periods of Years (as per error its not). maintain the same in Source system and transfer Global settings in BW to copy the same into BW system.
@AK -
Error - Excise modvat accounts not defined for DLFC transaction and 01 exci
Dear All,
Getting below error while doing J1IIN - Posting Excise invoice for Sale.
"Excise modvat accounts not defined for DLFC transaction and 01 excise group"
I checked with the settings GL are assigned to for DLFC and 01 excise group.
Is anywhere else I need to mantain the modvat GL
Regards,
RakeshCheck if you are using any subtransaction type along with excise transaction type.
Excise group, ETT, company code, sub transaction type (if any), Chart of account, Modvat account (pls maintain all the entries over here) search for modavat clearing field and maintain it.
BR
Edited by: Sujoy on Jan 15, 2010 9:45 AM
Maybe you are looking for
-
How to sync without losing artwork
I turned on match on devices and now with itunes it's a pain to get artwork sync between itunes on imac and my ipod touch, The ipod loses a lot of album artwork. What did apple di with itunes? can't now drag an album to ipod touch and get it there wi
-
I was thinking to unlock my phone and use it to test my apps on my phone, but I don't have any other phone. so I have only option to use my personal Hotmail id on my unlocked developer windows phone. But I am scared of losing my personal data. So i w
-
Hi, Currently SAP delivers role upload tool to upload the roles,transactions,miniapps etc... to portal. It works fine. we have a requirement that when the transaction is uploaded, the iview that is created should have the NAME: "transaction descrip
-
Itunes store is not loading after update to ios 7
I have an iphone 4s. I have recently updated to ios 7 and ios 7.0.2. The iTunes Stores is not loading anymore. I have signed in and out several times but it does not work. Any help? Tks.
-
Does anyone Bravia XBR-55x850c gets extremely hot on the bottom surface of the TV?
Bottom surface of the X850c gets extremely hot to the touch. Does anyone have similar issue? Or maybe it's normal? Please let me know. Thanks