For the k4 fiscal year variant,no period is defined 26-03-2010

Dear all,
Please explain thes eterms.
this error comes during making of purchage order.
why this error is coming and what i have to do???
Thanks and regards,
Baiju

Hi
Check what fiscal year variant is assigned to your company code in OB37 and check its validtiy in OB29
Regards
Antony

Similar Messages

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

Opening activities for the ne Fiscal Year

Dear All
what are the activities that are required to carry out for opening the New Fiscal Year..
Thanks & Regards
Veena Kunthe

Hello
The new fiscal year is automatically opened when you make your first posting in the new fiscal year or once the balance carried forward program has been run. You do not have to close the old fiscal year before you can post data in the new one. You therefore do not need to create closing or opening financial statements.
The prerequisites for posting to a new fiscal year are as follows:
If you are using a fiscal year variant which is year-specific, you first have to create a variant for this fiscal year and assign it to the relevant company code. See Fiscal Year and Calendar Year
If you have also defined year-dependent document number assignment, you must have already set up the document number ranges for the new fiscal year. For more information, see Document Number Assignment
The relevant posting periods must be open in the new fiscal year. See Opening and Closing Posting Periods
Check this link for more documentation on carry forwarding balances
http://help.sap.com/erp2005_ehp_02/helpdata/en/96/8b307143ce11d189ee0000e81ddfac/frameset.htm
Reg
assign points if useful

ABST2 - How to take the report for the previous fiscal year

Hi,
For FI-AA reconciliation, my scenario is this: The current fiscal year is 2009 and the system (server) date is 16-Apr-2009. My fiscal year period is: Mar-Apr. In ABST2, it does not accept Fiscal year. When I take the report, it displays for fiscal year 2009, which I don't want because I want it for the fiscal year 2008 to reconcile between FI and AA. The fiscal year 2008 is not yet closed in both FI and AA, so I want the report for 2008 only. But ABST2 always gives the report for the current fiscl year. Is there any way out to get the report for 2008?.
Thanks,
Kannan S

This report is based on the actual values. In the past this report was used for EURO conversions to see if the values are in line. When not it was not possible to do the euro conversion.
Normal it is a part from the fiscal year closing

Withholding Tax not picking for the current Fiscal year 2014

Dear Gurus,
Withholding tax assigned to the vendor is getting picked up for the fiscal year 2013 but when the same vendor is invoiced for year 2014 with the same WHT tax code we could see that there is no tax line getting generated against the Vendor. All the configurations related to WHT are verified. As far as i Know we will not maintain any end date for WHT tax code. request yout to advance.
Thanks in advance.
Thanks & Regards
Srikanth

hi,
Please check below mentioned Path - and check date from & to given period
SPRO- Financial Accounting (New) - Financial Accounting Global Settings (New) -Withholding Tax -Extended Withholding Tax - Company Code -Assign Withholding Tax Types to Company Codes
select WHT type against Company code -
W/tax obligated frm 01.04.2010 Oblig.to w/tax until 31.12.2999
and check vendor master data -
Thanking you
Regards
Mahesh

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

Fiscal year variant is incorrect

Dear all,
we have an additional daily ledger and daily fiscal year variant related to each other.
While trying to see line items by double-clicking, for example, cumulative balance line in FAGLB03 transaction I get the following error:
"Fiscal year variant XX is incorrect."
When determining the posting period, a period was found that is not in the permitted area 1 - 16.
Procedure Correct the fiscal year variant.
I have checked settings for the daily fiscal year variant and see no mistakes there.
I should mention that daily ledger and daily fiscal year variant had been set 2 years ago and worked without any problems.
Regards,
Stanislav.

Hello,
Check the customizing of LR variant in OB29
select the LR and double click the folder for period on the left.
enter then the year and continue
you will see a list of periods (hopefully, if not you have to maintain the Periods, better ask the FI colleague to do it).
Thanks
sapman man

Fiscal Year Variant

HI,
I tried creating PR using ME51N , after i entered the material no and plant details , i get an error message
"For the fiscal year variant, no period is defined for 03/26/2009" , my delivery date is April 1 , 2009.
Kindly suggest me wat i sud do to get rid of the error message..
Thank you in advance

Go to OB29 and select your Fiscal year variant and click on period and enter the year 2009 and maintain the periods as below
1     24     1     0
2     21     2     0
3     28     3     0
4     25     4     0
5     23     5     0
6     27     6     0
7     25     7     0
8     22     8     0
9     26     9     0
10     24     10     0
11     21     11     0
12     31     12     0

Multiple Fiscal Year Variant in the same client in SEM-BCS...

I have already looked at some earlier threads relating to this but didn't get a convincing answer to what I would like to know.
We have had a working SEM-BCS system with fiscal year variant K4. There was no need for defining leading fiscal year variant and none was defined. SAP, by default takes, K4 as the leading fiscal year variant.
Now there is a requirement for going on a different fiscal year variant for which we have created another databasis (there were a few other reasons besides these) with the same InfoObjects that we used earlier but with different fixed parameters, one of which is fisc year variant V9. Soon, we started experiencing bizarre dumps in the configuration which ultimately convinced me to define a leading fiscal year variant. I was reluctant to do so because there is a lot of old data (which will become 'historical' from new data basis point of view) from the working system on K4 that would still need to be reported on even when we have new BCS solution in the new fiscal year variant V9. That is not going away. There is a need to keep the old data for reporting (hence the rationale for a different data basis among a few others).
Since earlier Master Data was configured in the old fisc year variant K4, now I have defined the leading fiscal year variant as V9 so that MDF can appropriately identify the period dependency.
I would like to know if any of you have had an unexpected behavior from the system going forward. Does the system dump out when you try to read the old data (from earlier K4).
I have tried to explain the dilemma as clearly and succinctly as possible but if you need more clarifications, please do let me know.
I would really appreciate your help in this.

Is your requirement is that K4 to be changed to Z5.
The best way you can do it is in the transformation. Instead of directmapping,
Write a code like this in the trransformation to the cube
If SOURCE FIELD - 0FISCVAR eq 'k4'.
SOURCE FIELD - 0FISCVAR = 'Z5'.
I dont think we can change th data in the query being displayed. we can change the keyfigure values in query by frmulas etc...
but for a characteristic, i think we will be able to restrict bt not change the value.
to obtain the requirement, w have to get the data change before query designer that is in the cube leve.
Hope this helps,
Sri...

Can a weekly fiscal year variant have different number of posting periods?

Hi Friends,
Our demand planning team needs a weekly fiscal year variant (X) that will be assigned to all material master data. X is year dependent and needs to be consistent with our fiscail year variant Y which is assigned to all company codes.
I input "52" as number of posting periods for X, but the problem is: every 6 years, there is an additional week in this fiscal year.
This means, the number of posting period is also year dependent. Although most of fiscal years have 52 posting periods, some will have 53 posting periods instead.
I cannot create another fiscal year variant Z just for these 53 posting periods, because the material master data is not year dependent, I can only assign either Y or Z.
Have you ever encountered this situation? If so, could you please share your solution?
Thanks,
Jennifer

You can always have 53 period year independent fiscal year variant as explained below.
We have 365 days in normal year, and 366 days in leaf year(comes every 4 years).
In leaf year you will get 8 days in period 9 and 1 day in period 53.
In normal years all periods 7 days and 1 day in period 53
Month       Day       Period
1                    7             1
1                   14            2
1                   21            3
2                   25            8
3                   4              9
12                 23           51
12                 30           52
12                 31           53
You can have the same Fiscal year variant always.
Hope this will workout for you
Prasad
Edited by: Prasad Yarra on Nov 5, 2009 10:17 PM
Edited by: Prasad Yarra on Nov 5, 2009 10:54 PM

Defining the Fiscal Year Variant

Would someone explain the procedure for setting up the Fiscal year variant in the current version please.
The version I had used was 3.1h and the screens are now different. In 3.1h one simply copied the fiscal year variant (T.code OB29) using the copy command and one got a copy fiscal year dialog box in which one entered the data into the four fields. But none of this now happens.
In both the current version and the old version (3.1h) I select in column FV "V3" ( the Fiscal year variant I want ) copy V3 and now I want to create a new Fiscal Variant with my own company two letter designation (e.g. YZ) taking the V3 copy as the model to use. But I can't because nothing then happens.
In v3.1h a small sub window appeared when doing the copy ("copy icon") and in the first line was the copied designation code V3 with the description in the 2nd line and in the 3rd line one enterd one's own two letter company designation (e.g. YZ) plus the discription on line 4, click the tick and it was done.
How do I do that part now? Because this sub screen does not now appear when trying to do a copy and create a copy designation.

Hi Ton,
In transaction code OB29 for the later versions of SAP (i.e. 4+), you don't get a pop-up window. The system just copy the selected Fiscal Year Variant. That is the only one you would see once you have highlighted the year variant you want to copy from and you hit the "Copy" icon. All the fields you need to change would still be open. In the FV column, just change it from V3 to your new one YZ. Do the same for the description and the rest of the field you need to change and hit "Enter" on your keyboard. A diaglog box "Specify object to be copied" would appear. You can then "Copy All" or "only Copy Entry" depending on your need. If you select "Copy All", you would get a dialog box informing you of the number of dependent entries copied. You can then save your entries and carry out the rest of the set-up for "Periods", "Period Texts" and "Shortened Fiscal Years" as required by you.
I hope the above helps.
Do not forget to award the points please.
Regards,
Jacob

Fiscal year variant is not maintained for calendar year 2009

Hi,
After upgrade to BI 7.0 we are getting error: "Fiscal year variant & is not maintained for calendar year 2009" while opening a query through Bex Analyzer.
Basically it is happening like when we open a particular query, the Variable selection screen comes up, then on clicking the exection button (after selection) it shows SYSTEM_FAILURE exception & clicking the details button, shows the message ""Fiscal year variant is not maintained for calendar year 2009"
Please provide some information/resolution to this.
Thanks,
Shantanu.

HI,
Please ensure that you have defined your fiscal year variant in OB29
correctly. It is necessary that:
1. the previous year has been maintained,
2. an entry for Dec 31 exists in each fiscal year,
3. the following fiscal year has been maintained.
Hope this helps.
Regards,
Nitin

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

Data load : The source of the fiscal year variant has changed

I am loading some sales data from BW to APO and I keep getting this message .
The source of the fiscal year variant has changed
I am not sure how to resolve it because the help also does not give much info on the solution.
Thanks

Hi
it may be becoz
In R3 the Fiscal year variat has been changed .. Check the Fiscal year variant for ur precious data..and talk to ur functional team abt variant...
Normally for a comapny Fiscal year variant will be unique. I will change when there are some huge changes happend Merger,acqucsition etc..
hope it helps
regards
AK

Turkey: year end close RFSUMB00 / fiscal year variant

Hello guys,
I am wondering if anyone of you have had this requirement before.
Running RFSUMB00 on a Turkish company code will blow away the balances from all G/L accounts so that each individual account has a balance of 0.
Questions:
1. How do you manage revenue accounts (cost element categories 11 and 12). A pure cost centre is not enough as CO account assignment. You can switch off error message KI 166 (so that no COPA documents are then created), but is this really wanted?
2. If each individual account has a balance of 0 at year end, how to create a B/S and P/L for that year? Especially, for previous years? The only thing that comes to my mind is using special periods (13 to 16), but.... -->
3. ...in our system, the FI fiscal year variant is not K4, but a custom variant. The fiscal year (of the group) does not end on 31st December. I have a small FI-SL application running in the background (with K4 assigned there), and I could change the FI-SL period to 13 during the document transfer easily, but I ask myself why I do not post all of these funny closing documents directly in FI-SL then? This would save me from the usage of dummy assets/customers/vendors and the continous changes made to the "automatic postings only" flag (SKB1-XINTB).
Turkey experts, any hints welcome. What are your best practices?
Thank you,
Csaba

Yes frank,
GL closing should be carried only after all the sub ledgers are closed
for asset closing
you should open the new fiscal year first (AJRW) and then close the existing fiscal year. (AJAB)
otherwise FI-AA and Fi-GL may not reconcile (use tcode ABST2 to check this)
Regards
Sach!n
Edited by: Sachin Bhutani on Jan 30, 2010 3:32 AM

For the k4 fiscal year variant,no period is defined 26-03-2010

Similar Messages

Maybe you are looking for