Fiscal error

Hi All,
I've confiured a personnel area , personnel subarea, and employee group for my company.
Now after configuration when i'm hiring an employee for the same, it giving me a error at the
infotype 584 (Income from other Source) that Fiscal year not defined for 99 in Year that after this
i'm not able to proceed further.
Could any one help me out regarding this.
Regards,
Nidhi Khandelwal

Hi,
Assing the company code to fiscal year in this table V_001_U. If your country grouping is india for you need to assign the V3 fiscal year. If your country is usa for that you need to assign the K4.
Already stanard fiscal years are there. If you create the new fiscal you can create in your requirement way.
Good luck.
Devi

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

'Fiscal year period not expected error in BI 7.0

Hi Guys,
When I am loading data into Target(DSO, CUBE) It gives a error 'Fiscal year period not expected'. I got same error when I am loading into any target. Source is ECC 6.0 and Target is BI 7.0. I am extracting the data from FI/CO module. Could you pls help on this.
Warm Regards,
G N

Is that error 'Fiscal year period not expected' or 'Fiscal year variant K4 not expected'
If it is 'Fiscal year variant K4 not expected', then try the following
In BI, select source System --> Transfer Global Settings (OR)
In transfer rules, select filed '0FISCVARNT' ---click on 'Tp' .... select radio button 'Constant' and enter K4..save & activate. (OR)
in ECC -- SE16--> check wether table T009 has value K4..If not enter new value (K4)

Error while entering the Fiscal Year/Period Variable

I keep getting the following error message when I try to input or select the Variable on the report that has been executed on the Portal. Everything is fine when done through Bex.
<b> Please enter value in permitted format for variable Fiscal Year/Period (Selection Options, Optional).
Entry needs template ___/____
For characteristic , enter value in a permitted format</b>
Would anybody have any clue as to why?? It does have the Fiscal year Variant.
Thanks

This is fxed in BI JAVA SPS 12 Patch 2. Not sure whether there is any OSS notes for earlier SPS.

Fiscal Year Change in MM failing with error message

Hi I am with a company that is using SAP R/3 ECC6 Modules SD MM FI CO with COPA (costing based) for reporting. Our fiscal year runs 1 August to 31 July. I am a FICO support analyst, currently also filling in for SDMM until we complete recruitment of a new person in that post.
In MM when trying to open the new period/close the old, we are getting the error message 'The specified year 2009 is not the current calendar year.' the detailed log says 'incorrect period in control record of CoCo. The current period (month/year is 112008)
I have:
1) Maintained our FYV in the IMG and it is set to year independent (tried making it year dependent but that didn't solve the problem)
2)Set the apppropriate periods with correct year shift and texts
3) Assigned the CoCode to the FYV
4) Checked that the proper variant for posting periods are set.
5) Set the Global parameters for the CoCode
Financial postings work fine and there seems to be no problem with the FYV there, and everything worked Ok last year (our first with SAP since Go Live).
I have searched the relevant sections in my SAP Press config manuals for FI and MM and done a search on Google but there must be something I am missing.
Can anyone suggest a solution, please.
Thanks in advance
David

Thanks anyway, Vijay, but OB52 is for changing Fiscal periods. That table is set correctly, the financial postings wouldn't be working if it wasn't.
I hadn't checked OMSY, Syed, thank you for that suggestion. There are no entries in any of the fields for Year or FYr. I am willing to make entries here to try it if there is a good reason but why would it have worked all through FY2008 without any entry in these fields but fail now in the new FY? The period change worked without problem for the past 12 months, isn't this the same as most SAP fields i.e. if you enter nothing then it is open for everything, in this case all years?
I am using MMPV to try to open the new period but it is there that I am getting the error messages.
Edited by: David Crossley on Aug 11, 2008 1:00 PM

Error in Timebucket while using Fiscal Week

We have a requirement to run deployment to create deployment
orders weekly. Hence we copied 9ANSNP94 and want to change the timebucket.
The weeks definition over here is not the same as SAP Std.
E.g
Start Date
End Date
Week Number
1-Jan-13
6-Jan-13
Week 1
7-Jan-13
13-Jan-13
Week 2
14-Jan-13
20-Jan-13
Week 3
21-Jan-13
27-Jan-13
Week 4
28-Jan-13
31-Jan-13
Week 5A
1-Feb-13
3-Feb-13
Week 5B
4-Feb-13
10-Feb-13
Week 6
11-Feb-13
17-Feb-13
Week 7
18-Feb-13
24-Feb-13
Week 8
25-Feb-13
28-Feb-13
Week 9A
1-Mar-13
3-Mar-13
Week 9B
Hence we have defined Fiscal year variant
upto 62 periods
But get error in timebucket –
Can you please help to resolve the issue
Regards
Nishigandha
Start Date
End Date
Week Number
1-Jan-13
6-Jan-13
Week 1
7-Jan-13
13-Jan-13
Week 2
14-Jan-13
20-Jan-13
Week 3
21-Jan-13
27-Jan-13
Week 4
28-Jan-13
31-Jan-13
Week 5A
1-Feb-13
3-Feb-13
Week 5B
4-Feb-13
10-Feb-13
Week 6
11-Feb-13
17-Feb-13
Week 7
18-Feb-13
24-Feb-13
Week 8
25-Feb-13
28-Feb-13
Week 9A
1-Mar-13
3-Mar-13
Week 9B

Thanks ada
It worked really well. Now I can see the fiscal weeks in planning book.
But the period is displayed as P13.2014, I want this to be viewed as per the period Text.
I have defined the text in the fiscal year varaint configuration
Do I need to use the user Exit - APODM006 or is there any std way?
Start Date
End Date
Period
Week Number
1-Jan-14
5-Jan-14
1
Week 1
6-Jan-14
12-Jan-14
2
Week 2
13-Jan-14
19-Jan-14
3
Week 3
20-Jan-14
26-Jan-14
4
Week 4
27-Jan-14
31-Jan-14
5
Week 5
1-Feb-14
2-Feb-14
6
Week 6
3-Feb-14
9-Feb-14
7
Week 7
10-Feb-14
16-Feb-14
8
Week 8
17-Feb-14
23-Feb-14
9
Week 9
24-Feb-14
28-Feb-14
10
Week 10A
1-Mar-14
2-Mar-14
11
Week 10B
3-Mar-14
9-Mar-14
12
Week 11
10-Mar-14
16-Mar-14
13
Week 12
17-Mar-14
23-Mar-14
14
Week 13
24-Mar-14
30-Mar-14
15
Week 14
31-Mar-14
31-Mar-14
16
Week 15A
1-Apr-14
6-Apr-14
17
Week 15B

While activation of DSO error SID genarati No fiscal year variant specified

Hi all,
While activationg the DSO i am getting error called SIDgenaration " No fiscal year variant specified"
I have checked the PSA fiscal year variant is avilable..
How to solve this error please somebody let me know ASAP
Regards
Kiran

Hi.......
For some particular value of Fiscal variant it is failing............ in ODS activation.......in the log it will not show that value...........but if load fails due to SID issue then log generally shows the particular value.......
You load the master data for fiscal year varinat .........then activate it.......using program.......RSDDS_AGGREGATES_MAINTAIN..........then tepeat the ODS activation.......this is to run attribute change run.............you can also do it from RSA1........
You can also change the said settings in the above post..........but it should'nt done in PROD........
Hope this helps.....
Regards,
Debjani.........

I am getting error with Fiscal Year Period

Hi Gurus
When i am loading data into Data Target from ODS i am getting this error
Time conversion from 0CALDAY to 0FISCPER (fiscal year Z1 ) failed with value 02000801
Can u please help me to solve this issue
Thanks & Regards
Mahi

There is somthing wrong in 0calday value (02000801); it should be 20000801 fro first of augost 2000.
Che data in your ODS.
Hope it helps.
Regards

Change fiscal year to 2006 in Asset Management : error in year-end closing

SAP version: 4.0B
Transaction Codes used: Year-end closing AJAB, Fiscal year change AJRW
We are trying to change the fiscal year to 2006 in Asset Management.
I tried to change the fiscal year to 2006 for the company code 0055 using transaction code AJRW. The test run has displayed an error message Fiscal year change in co. code 0055 1 possible only after year-end closing 2004 2.
I have used the transaction code OAAQ to find the out the fiscal year, the closing for depreciation area is successfully performed.
Unfortunately it is still showing 2003 which should have been 2004 for company code 0055.
I tried to close the fiscal year 2004. The test run has completed successfully. I have scheduled the RAJABS00. The program has executed successfully with no errors or warnings.
The closing for depreciation area (Transaction OAAQ) is still showing 2003 for company code 0055, which should have been changed to 2004.
I am new to Asset Management. Can you please give some suggestions on how to fix the problem and change the fiscal year to 2006.
Thank you,
Vidya

Hi,
Thank you very much for your prompt reply.
I have used transaction OAAR to check if any area is still open for previous years.
Surprisingly! The areas are closed only till 2003.
Can you please let me know what to do (transaction codes - programs) to close the areas for fiscal year 2004.
I am new to Asset Management. I think you are good in Asset Management. Can you please give some suggestions on how to close the fiscal year 2004.
Can you please let me know if I have to run any other transactions other than closing the areas before running the transaction to close the fiscal year 2004.
Thank you very much.
Sincerely,
Vidya

Best practice Error " no fiscal year "

In best practice Report CR " GL Statment " After updating the data base and entering the parameters , It pops to me error " no fiscal year variant specified " though i run the same query in the ERP with the same parameters and it runs !
And am using Crystal Reports 2008 , version 12.1.0.892 . This Report in SAP BEST PRACTICE

Did you configure the additional data sources and the BP package itself as described in the BI QUick guide and the Add additional data sources document included in the package?
Regards,
Stratos

BAPI_PO_CREATE1 Error related to Fiscal year variant

Hi,
I am working on open PO tranfer program.
initialy i have created one PO from ME21n tcode, and its worked out fine
now using same data when i creating PO using BAPI -> BAPI_PO_CREATE1 then i am getting following error
E No instance of object type PurchaseOrder has been created. External reference:
E Purchase order still contains faulty items
W Purchase order date is in the past
I Order unit ****** cannot be used
I Date / / period is not valid
E For the Z6 fiscal year variant, no period is defined for / /
I Net price for item 00010 adopted from last document
Wondering why error "For the Z6 fiscal year variant, no period is defined for / / " not triggered in ME21n ?
From excel i am passing below item data:
1. wa_data-ebelp
2. wa_data-ematn
3. wa_data-menge
4. wa_data-meins
5. wa_data-netpr
Please look into below code...
    LOOP AT it_data INTO wa_data WHERE ebeln = wa_header-ebeln.
*     PO Item data
      wa_poitem-po_item     = wa_data-ebelp.
      wa_poitem-short_text = wa_data-txz01.
      CALL FUNCTION 'CONVERSION_EXIT_MATN1_INPUT'
        EXPORTING
          input              = wa_data-ematn
        IMPORTING
          OUTPUT           = wa_poitem-material
*       EXCEPTIONS
*         LENGTH_ERROR       = 1
*         OTHERS             = 2
      wa_poitem-plant         = 'U001'.
      wa_poitem-stge_loc      = 'M001'.
      wa_poitem-quantity      = wa_data-menge.
      wa_poitem-po_unit       = wa_data-meins. "001
      wa_poitem-net_price     = wa_data-netpr. "001
      wa_poitem-price_unit    = wa_data-peinh. "001
      wa_poitem-prnt_price    = c_x.
      wa_poitem-order_reason = 'PB'.
      wa_poitem-vend_mat      = wa_data-idnlf. "Vend Mat num
      wa_poitem-period_ind_expiration_date = 'D'.
      APPEND wa_poitem TO it_poitem.
      wa_poitemx-po_item      = wa_data-ebelp.
      wa_poitemx-short_text   = c_x.
      wa_poitemx-material     = c_x.
      wa_poitemx-plant        = c_x.
      wa_poitemx-stge_loc     = c_x.
      wa_poitemx-quantity     = c_x.
      wa_poitemx-po_unit      = c_x. "001
      wa_poitemx-net_price    = c_x. "001
      wa_poitemx-price_unit   = c_x. "001
      wa_poitemx-prnt_price   = c_x.
      wa_poitemx-order_reason = c_x.
      wa_poitemx-vend_mat     = c_x.
      wa_poitemx-period_ind_expiration_date = c_x.
      APPEND wa_poitemx TO it_poitemx.
*     PO Delivery schedule data
      wa_poschedule-po_item = wa_data-ebelp.
      wa_poschedule-delivery_date = wa_data-eindt.
      APPEND wa_poschedule TO it_poschedule.
      wa_poschedulex-po_item = wa_data-ebelp.
      wa_poschedulex-delivery_date = c_x.
      APPEND wa_poschedulex TO it_poschedulex.
ENDLOOP.
Please suggest what went wrong?

here is the sample code
this my sample code to create PO with BAPI,
DATA : lwa_bapimepoheader TYPE bapimepoheader
,lwa_bapimepoheaderx TYPE bapimepoheaderx
,li_bapimepoitem TYPE STANDARD TABLE OF bapimepoitem
,lwa_bapimepoitem TYPE bapimepoitem
,li_bapimepoitemx TYPE STANDARD TABLE OF bapimepoitemx
,lwa_bapimepoitemx TYPE bapimepoitemx
,li_conditions TYPE STANDARD TABLE OF komv
,li_return TYPE STANDARD TABLE OF bapiret2
, n TYPE c
PARAMETERS: p1 TYPE c AS CHECKBOX.
IF p1 = 'X'.
lwa_bapimepoheader-doc_type = 'NB'.
lwa_bapimepoheader-purch_org = 'NA00'.
lwa_bapimepoheader-pur_group = 'C02'.
lwa_bapimepoheaderx-doc_type = 'X'.
lwa_bapimepoheaderx-purch_org = 'X'.
lwa_bapimepoheaderx-pur_group = 'X'.
lwa_bapimepoitem-po_item = '10'.
lwa_bapimepoitem-material = '000000000000020111'.
lwa_bapimepoitem-plant = 'CA01'.
lwa_bapimepoitem-vend_mat = '1000'.
lwa_bapimepoitem-quantity = '10'.
lwa_bapimepoitem-orderpr_un = 'M'.
lwa_bapimepoitem-no_more_gr = 'K'.
lwa_bapimepoitem-agreement = '4600000095'.
lwa_bapimepoitem-agmt_item = '10'.
lwa_bapimepoitem-pricedate = 'X'.
lwa_bapimepoitem-price_date = '20071030'.
lwa_bapimepoitem-no_rounding = 'X'.
APPEND lwa_bapimepoitem TO li_bapimepoitem.
lwa_bapimepoitemx-po_item = '10'.
lwa_bapimepoitemx-po_itemx = 'X'.
lwa_bapimepoitemx-po_itemx = 'X'.
lwa_bapimepoitemx-material = 'X'.
lwa_bapimepoitemx-plant = 'X'.
lwa_bapimepoitemx-quantity = 'X'.
lwa_bapimepoitemx-po_unit = 'X'.
lwa_bapimepoitemx-orderpr_un = 'X'.
lwa_bapimepoitemx-acctasscat = 'X'.
lwa_bapimepoitemx-agreement = 'X'.
lwa_bapimepoitemx-agmt_item = 'X'.
lwa_bapimepoitemx-pricedate = 'X'.
lwa_bapimepoitemx-price_date = 'X'.
lwa_bapimepoitemx-preq_no = 'X'.
lwa_bapimepoitemx-preq_item = 'X'.
lwa_bapimepoitemx-no_rounding = 'X'.
APPEND lwa_bapimepoitemx TO li_bapimepoitemx.
DATA: lo_msg_handler TYPE REF TO cl_message_handler_mm.
CALL METHOD cl_message_handler_mm=>get_handler
IMPORTING
ex_handler = lo_msg_handler.
lo_msg_handler->remove_all( ).
lo_msg_handler->cleanup( ).
CALL FUNCTION 'BAPI_PO_CREATE1' "in background task
EXPORTING
poheader = lwa_bapimepoheader
poheaderx = lwa_bapimepoheaderx
testrun = 'X'
NO_MESSAGING = c_x
NO_MESSAGE_REQ = c_x
no_authority = 'X'
IMPORTING
expheader = lwa_bapimepoheader
TABLES
return = li_return
poitem = li_bapimepoitem
poitemx = li_bapimepoitemx
conditions = li_conditions.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

Error in opening Fiscal Year by Dep. Area

Hi All,
We have following Depreciation Areas:
01 - Book Depreciation and 10,11,12 & 13 for Tax Depreciation.
I am trying to open Fiscal Year 2014 for Tax Depreciation Area only by using T-code OAAR, system is giving me below error message:
You also have to change the close of depreciation area 01
Message no. AC433
Diagnosis
Depreciation area 10, for which you want to reset the year-end closing, is linked to depreciation area 01.
This could be because the areas are linked due to:
Identical acquisition and production costs (value takeover)
A derived depreciation area
Procedure
Correct your entries. You can only modify the area for which you received the message.
I checked setting of t-code OABC:Dep. Area 10 is having ValAd as 01, this is the reason system is not allowing to Open Fiscal Year 2014.
Please throw some insight how I can open fiscal Year 2014 for Tax Areas only.
Thanks & Regards,
Vivek

Hi George,
Thanks for helping me out. There was no identical check on OABC for area 10.
Upon researching more I found that there are other depreciation area which is only for reporting, are deriving values from Dep Area 10 and 01.
Therefore system was throwing error to open Fiscal Year for 01 as well. I have removed the derivation from dep area used for reporting only and try to open Fiscal Year for Tax Area, now system allow me to open it by Area.
This issue is resolved. Thanks again for your help.
Regards,
Vivek

The error showing as Fiscal year change has not carried out for the coCd

Hi all,
I am facing a very critical situation. My client has the last closed fiscal year as 2006(from 2006 april to 2007 march).For the fiscal yr. 2007(2007april to 2008 march) they have already finalised and submitted the reports made from some parallel software.They now want to tally this report with SAP system and to adjust the SAP system entries as per this report.This work was running fine.But on 01.04.2009 none of the asset reports are running.The error it's throwing is as-
Fiscal year change not yet made for company code PWAL
Message no. AB059
Diagnosis
You have not yet carried out a fiscal year change for company code PWAL, although the current system date is in the new fiscal year.
Procedure
Carry out the fiscal year change for company code PWAL.
Proceed
The error is quite understandable.We have to close 2007 and then perform the fiscal year change.But the problem is that the adjustment for the year 2007 is not yet complete.Is it the only solution with me that I should close the yr.2007 and again open it after the fiscal yr. change? If that is done can I take care of the adjustment in the posted depreciation? Or is it possible that the system date can be made back to 31.03.2009(very stupid ask!). The real problem is that my client has mistakely created some assets in the year 2007(by AS91 after changing the take over date) those should have been shown in the next year and also some assets are creted in the year 2008 by the same strange method those should be shown in the year 2007.What I am doing now is deleting these legacy assets and creating the new assets in the correct year.And this process is not yet complete.If I close the year 2007, then the depreciation of these legacy assets will also be posted.Later how can I reverse the effect?Also without seeing the reports I can't make the adjustments.Please suggest/advice.
Debabrata

Hi Debabrata,
You have to do all fiscal year closing steps for 2007. When you reopen it you can do a repeat run for 2007. (You can do the reapeat run only for the new/ changed assets.)
Try first to test this in an actual test system (document it and do the same in production). Perhaps as you know when 2009 is open I want to close 2008 in one week. All changes they make in the asset system (change depreciation keys, recalulating,...) can result in postings in 2007 / 2008 what they don't want and later fiscal year problems. You will found a lot off masages about this on the form.

Fiscal year closing error

Dear Expert,
When I was trying to run AJAB to close fiscal year 2007 and I got an error message
"The planned depreciation was not completely posted to Financial Accounting for asset 017000000000-0000 in company code 0011 in depreciation area 01u201D
Actually this asset is goodwill, it was created in year 2007 and amortized for one year but in year 2008 due to IFRS not allow to amortize goodwill so the depreciation key was changed to "0000" no depreciation.
When I try AFAB for this particular asset for period 12 for 2007 and I got message that it can only be run in period 13. So I change the period to 13 and I see a report for depreciation to be posted. Under the planned column is 0, posted column is the accumulated depreciation figures and to be posted is a reverse amount of the posted column. This means it will reverse the accumulated depreciation of year 2007.
What's worng with it? This goodwill should be depreciated in year 2007 and only 2008 not to be depreciated? Any way can go directly to the table and change the figures so that no posting is needed?
I am using SAP R/3 4.6C
thank you
max

Max,
Shall I suggest you a way to handle this situation? Please go ahead and check the "Shut Down" Indicator after adding an interval with the date beginning 2008.
Use T-code AS02, go to Time-dependent. Click on Add Interval under More Intervals and add the beginning date of FY2008. Then check the Asset Shut down indicator. You can change the Depr key back to the old one. See the results of this change in AW01N.
The reason why the system is reversing the depr already posted is that you have selected the depr key 0000, which means no depreciation throughout life.
Please revert in case you have any questions.
Regards,
Vinod

Fiscal error

Similar Messages

Maybe you are looking for