Fiscal variant error

Hi All
I got an error query execution by SAP BEX " value 000 is invalid for the fiscal year variant ".
Thanks Prasanna

Hi Prasanna,
If you are using any SAP EXIT or Customer exit for Fiscal variant, just check the values for the same '000' may not be executed in the routine.If the value exists for Fiscal variant and it is not required for report just do a selective deletion at cube level and try to execute the query.
Hope this helps.........
Rgs,
I.R.K

Similar Messages

Fiscal Week and Fiscal Variant Creation in BW

Hi,
I have a 2004s system that is not connected to an R/3/ECC client. The data comes from a SQL Server Database. We need to report on a fiscal week basis and not a calendar week.
We have a seperate calendar week that finance uses, but operations uses a different work week (Tues - Mon).
I figure the best way to handle this is by creating a Fiscal Variant of 53 periods (one for each week). My problem is that I cannot right click on the R/3 source system and import all of the Fiscal Periods. I have to create them in BI directly.
Can anyone advise me on how to do this? I have completed the following steps:
1.) I went into SPRO=> SAP NetWeaver=> Business Intelligence=> General BI Settings=> Maintain Fiscal year variant.
2.) Then I created variant ZA with Year-Dependent and 53 periods. I left special periods blank.
3.) I create the periods for 2007 and 2008 making 1/6/07 the last day of the first period of 2007 and 12/29/07 the last day of the last period of 2007 and one final entry for 12/31/07 for period 1 year shift +1. 2008 was set up similarly.
4.) I setup the period texts naming them as 1/ FW 1 ... to 53/ FW 53 for both 2007 and 2008.
5.) I then went into SHortened Fiscal Year and made both 2007 and 2008 to have 52 periods.
Am I missing something here? When I load my data I get the following error:
"Fiscal year variant ZA is not maintained for calendar year 2007" and I get this error on over 100 records of my 1300 record load. Some Dates are 2/18/08 which isn't in FY07 and others are 1/8/07 - 1/10/07.
Any help is appreciated.
Thanks,
Brian

Did you ever get an answer to your question? We are seeing the same issue.

Layout variant error

Please find code below. When I run this report with transaction it gives variant error .How can I fix this problem
REPORT yiwm_uom_stock                         .
*---Data Include
INCLUDE yiwm_uom_stock_data.
*INITIALIZATION.
PERFORM initialize_variant.
*----ON SELECTION SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_vari.
PERFORM f4_for_variant .
*---START-OF-SELECTION
START-OF-SELECTION.
PERFORM get_data.
PERFORM write_data .
*&      Form get_data
FORM get_data.
*--Quants of stock with selection screen.
SELECT werks lgort lgnum gesme
         verme einme ausme lgpla
         lgtyp matnr lqnum
    FROM lqua
    INTO CORRESPONDING FIELDS OF TABLE gt_itab
   WHERE werks IN s_werks
     AND lgnum EQ p_lgnum
     AND lgort IN s_lgort
     AND lgtyp IN s_lgtyp
     AND kober IN s_kober
     AND matnr IN s_matnr.
LOOP AT gt_itab.
    CLEAR lagp .
    SELECT SINGLE lgtyp lgber lptyp plauf skzua skzue skzsa skzse
                   skzsi spgru anzqu maxqu anzle maxle btanr btaps
                   kzdyn lgewi gewei mgewi bdatu bzeit ivivo sorlp
                   rdatu rzeit kzinv idatu ivnum ivpos brand uname
                   laedt kober reihf verif
             FROM lagp
      INTO CORRESPONDING FIELDS OF gt_itab
     WHERE lgnum = gt_itab-lgnum
       AND lgpla = gt_itab-lgpla
       AND lgtyp = gt_itab-lgtyp.
    CLEAR mara.
    SELECT SINGLE matnr meins zzshmat matkl
                  mtart ean11 zzkshrtyp
      FROM mara
      INTO CORRESPONDING FIELDS OF gt_itab
     WHERE matnr EQ gt_itab-matnr.
    CLEAR marm.
    SELECT SINGLE meinh umrez umren breit hoehe
                  meabm volum voleh brgew gewei
      FROM marm
      INTO CORRESPONDING FIELDS OF gt_itab
     WHERE matnr EQ gt_itab-matnr
       AND meinh EQ p_meinh.
    CLEAR mlgn.
    SELECT SINGLE ltkza ltkze lgbkz block
                  bsskz l2skr mkapv
      FROM mlgn
      INTO CORRESPONDING FIELDS OF gt_itab
     WHERE matnr EQ gt_itab-matnr
       AND lgnum EQ gt_itab-lgnum.
    CLEAR mlgt.
    SELECT SINGLE lgpla lpmax lpmin
                  mamng nsmng kober rdmng
     FROM mlgt
     INTO CORRESPONDING FIELDS OF gt_itab
     WHERE lgnum EQ gt_itab-lgnum
       AND lgpla EQ gt_itab-lgpla
       AND matnr EQ gt_itab-matnr
       AND lgtyp EQ gt_itab-lgtyp.
    CLEAR makt.
    SELECT SINGLE maktx
      FROM makt
      INTO gt_itab-maktx
     WHERE matnr EQ gt_itab-matnr.
    MODIFY gt_itab.
    CLEAR   gt_itab.
ENDLOOP.
ENDFORM.                    "get_data
     Form write_data                                              *
FORM write_data.
PERFORM find_list_header.
PERFORM fill_field_cat TABLES gt_fldcat
                         USING 'GT_ITAB'
                                'YIWM_UOM_STOCK'.
gv_repid = sy-repid.
gs_variant-report = sy-repid.
gs_variant-variant = p_vari.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_buffer_active    = ' '
      i_callback_program = gv_repid
      i_default          = 'X'
      i_save             = 'A'
      is_layout          = gs_layout
      it_fieldcat        = gt_fldcat[]
      is_variant         = gs_variant
    TABLES
      t_outtab           = gt_itab.
ENDFORM.                    " write_data
    Form find_list_header                                         *
FORM find_list_header.
CLEAR : gt_header, gt_header[].
gt_header-typ = 'H'.
sy-title = 'UOM STOCK REPORT'.
MOVE sy-title TO gt_header-info.
APPEND gt_header.
ENDFORM.                    " find_list_header
    Form fill_field_cat                                           *
FORM fill_field_cat TABLES gt_fldcat
                      USING p_intname
                            p_inclname.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
    EXPORTING
      i_program_name         = sy-repid
      i_inclname             = p_inclname
      i_internal_tabname     = p_intname
    CHANGING
      ct_fieldcat            = gt_fldcat[]
    EXCEPTIONS
      inconsistent_interface = 1
      program_error          = 2
      OTHERS                 = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " fill_field_cat
*&      Form INITIALIZE_VARIANT
      text
FORM initialize_variant .
g_save = 'A'.
CLEAR g_variant.
g_variant-report = sy-repid.
gx_variant = g_variant.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
    EXPORTING
      i_save     = g_save
    CHANGING
      cs_variant = gx_variant
    EXCEPTIONS
      not_found = 2.
IF sy-subrc = 0.
    p_vari = gx_variant-variant.
ENDIF.
ENDFORM.                               " INITIALIZE_VARIANT
*&      Form F4_FOR_VARIANT
      text
FORM f4_for_variant.
gs_variant-report = sy-repid.
gs_variant-variant = p_vari.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
    EXPORTING
      is_variant = gs_variant
      i_save     = g_save
    IMPORTING
      e_exit     = g_exit
      es_variant = gx_variant
    EXCEPTIONS
      not_found = 2.
IF sy-subrc = 2.
    MESSAGE ID sy-msgid TYPE 'S'      NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
    IF g_exit = space.
      p_vari = gx_variant-variant.
    ENDIF.
ENDIF.
ENDFORM.                               " F4_FOR_VARIANT
*&      Form PAI_OF_SELECTION_SCREEN
      text
FORM pai_of_selection_screen.
IF NOT p_vari IS INITIAL.
   MOVE g_variant TO gx_variant.
   MOVE p_vari TO gx_variant-variant.
   CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
     EXPORTING
       i_save     = g_save
     CHANGING
       cs_variant = gx_variant.
   g_variant = gx_variant.
ELSE.
   PERFORM initialize_variant.
ENDIF.
ENDFORM.                               " PAI_OF_SELECTION_SCREEN

Hi Narendan ..
I changed but it is already leave to the code screen (leave program). I think it will be useful to send complete code again .Please remember , it gives error only call with transaction.
REPORT yiwm_uom_stock                         .
*---Data Include
INCLUDE yiwm_uom_stock_data.
INITIALIZATION.
PERFORM initialize_variant.
*----ON SELECTION SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_vari.
PERFORM f4_for_variant .
*---START-OF-SELECTION
START-OF-SELECTION.
PERFORM get_data.
PERFORM write_data .
*&      Form get_data
FORM get_data.
*--Quants of stock with selection screen.
SELECT werks lgort lgnum gesme
         verme einme ausme lgpla
         lgtyp matnr lqnum
    FROM lqua
    INTO CORRESPONDING FIELDS OF TABLE gt_itab
   WHERE werks IN s_werks
     AND lgnum EQ p_lgnum
     AND lgort IN s_lgort
     AND lgtyp IN s_lgtyp
     AND kober IN s_kober
     AND matnr IN s_matnr.
LOOP AT gt_itab.
    CLEAR lagp .
    SELECT SINGLE lgtyp lgber lptyp plauf skzua skzue skzsa skzse
                   skzsi spgru anzqu maxqu anzle maxle btanr btaps
                   kzdyn lgewi gewei mgewi bdatu bzeit ivivo sorlp
                   rdatu rzeit kzinv idatu ivnum ivpos brand uname
                   laedt kober reihf verif
      FROM lagp
      INTO CORRESPONDING FIELDS OF gt_itab
     WHERE lgnum = gt_itab-lgnum
       AND lgpla = gt_itab-lgpla
       AND lgtyp = gt_itab-lgtyp.
    CLEAR mara.
    SELECT SINGLE matnr meins zzshmat matkl
                  mtart ean11 zzkshrtyp
      FROM mara
      INTO CORRESPONDING FIELDS OF gt_itab
     WHERE matnr EQ gt_itab-matnr.
    CLEAR marm.
    SELECT SINGLE meinh umrez umren breit hoehe
                  meabm volum voleh brgew gewei
      FROM marm
      INTO CORRESPONDING FIELDS OF gt_itab
     WHERE matnr EQ gt_itab-matnr
       AND meinh EQ p_meinh.
    CLEAR mlgn.
    SELECT SINGLE ltkza ltkze lgbkz block
                  bsskz l2skr mkapv
      FROM mlgn
      INTO CORRESPONDING FIELDS OF gt_itab
     WHERE matnr EQ gt_itab-matnr
       AND lgnum EQ gt_itab-lgnum.
    CLEAR mlgt.
    SELECT SINGLE lgpla lpmax lpmin
                  mamng nsmng kober rdmng
     FROM mlgt
     INTO CORRESPONDING FIELDS OF gt_itab
     WHERE lgnum EQ gt_itab-lgnum
       AND lgpla EQ gt_itab-lgpla
       AND matnr EQ gt_itab-matnr
       AND lgtyp EQ gt_itab-lgtyp.
    CLEAR makt.
    SELECT SINGLE maktx
      FROM makt
      INTO gt_itab-maktx
     WHERE matnr EQ gt_itab-matnr.
    MODIFY gt_itab.
    CLEAR   gt_itab.
ENDLOOP.
ENDFORM.                    "get_data
     Form write_data                                              *
FORM write_data.
PERFORM find_list_header.
PERFORM fill_field_cat TABLES gt_fldcat
                         USING 'GT_ITAB'
                                'YIWM_UOM_STOCK'.
gv_repid = sy-repid.
gs_variant-report = sy-repid.
gs_variant-variant = p_vari.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_buffer_active    = ' '
      i_callback_program = gv_repid
      i_default          = 'X'
      i_save             = 'A'
      is_layout          = gs_layout
      it_fieldcat        = gt_fldcat[]
      is_variant         = gs_variant
    TABLES
      t_outtab           = gt_itab.
ENDFORM.                    " write_data
    Form find_list_header                                         *
FORM find_list_header.
CLEAR : gt_header, gt_header[].
gt_header-typ = 'H'.
sy-title = 'UOM STOCK REPORT'.
MOVE sy-title TO gt_header-info.
APPEND gt_header.
ENDFORM.                    " find_list_header
    Form fill_field_cat                                           *
FORM fill_field_cat TABLES gt_fldcat
                      USING p_intname
                            p_inclname.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
    EXPORTING
      i_program_name         = sy-repid
      i_inclname             = p_inclname
      i_internal_tabname     = p_intname
    CHANGING
      ct_fieldcat            = gt_fldcat[]
    EXCEPTIONS
      inconsistent_interface = 1
      program_error          = 2
      OTHERS                 = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " fill_field_cat
*&      Form INITIALIZE_VARIANT
      text
FORM initialize_variant .
g_save = 'A'.
CLEAR g_variant.
g_variant-report = sy-repid.
gx_variant = g_variant.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
    EXPORTING
      i_save     = g_save
    CHANGING
      cs_variant = gx_variant
    EXCEPTIONS
      EXCEPTIONS
      wrong_input = 1
      not_found = 2
      program_error = 3
    OTHERS = 4 .
IF sy-subrc = 0.
    p_vari = gx_variant-variant.
ENDIF.
ENDFORM.                               " INITIALIZE_VARIANT
*&      Form F4_FOR_VARIANT
      text
FORM f4_for_variant.
gs_variant-report = sy-repid.
gs_variant-variant = p_vari.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
    EXPORTING
      is_variant = gs_variant
      i_save     = g_save
    IMPORTING
      e_exit     = g_exit
      es_variant = gx_variant
    EXCEPTIONS
      not_found = 2.
IF sy-subrc = 2.
    MESSAGE ID sy-msgid TYPE 'S'      NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
    IF g_exit = space.
      p_vari = gx_variant-variant.
    ENDIF.
ENDIF.
ENDFORM.                               " F4_FOR_VARIANT
*&      Form PAI_OF_SELECTION_SCREEN
      text
FORM pai_of_selection_screen.
IF NOT p_vari IS INITIAL.
    MOVE g_variant TO gx_variant.
    MOVE p_vari TO gx_variant-variant.
    CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
      EXPORTING
        i_save     = g_save
      CHANGING
        cs_variant = gx_variant.
    g_variant = gx_variant.
ELSE.
    PERFORM initialize_variant.
ENDIF.
ENDFORM.                               " PAI_OF_SELECTION_SCREEN

Time series inconsistency due to change in Fiscal variant/Storage bucket

Hi All,
We got into the situation where running time series consistency check on a DP planning area fails with the message pointing to, 'changes to Fiscal variant'. We are unable to track any changes to the fiscal variant though there is a possibility that storage bucket horizon could have been changed. Is there a way to correct/synch this by running a report?
We are trying to avoid re-initialization here, though this is an option, for the obvious reasons to backup the data in production. Is there an alternative solution to fix this inconsistency?
Cheers!

Dear Ashok,
You should never change a FYV when this FYV is used in a storage
bucket profile which is used in a planning area and if time series
objects are already created. It is no problem to maintain the FYV for
an additional time range, but changes and deletion of periods should
never be made if the FYV is actively used. You should not
change existing periods. If you want to make any changes to buckets
in your FYV or delete buckets, you should always make a COMPLETE
backup of ALL your data from the planning area into an InfoCube,
then delete the time series objects for the planning area (and with
this all the data in liveCache) and then change the FYV. After that,
you can create time series objects again and reload the data from the
Backup-InfoCube into the planning area. If you do these steps, you
will not risk to loose any data. The data in the InfoCube will be
the backup you can reload.
As some processes check the FYV some time before and after it is used,
it is very recommendable to maintain the FYV at least 2 - 3 years in
the past and in the future. E.g. if you create time series objects up
from 2001 you should maintain your FYV at least back to 1999 and if you
create time series objects until 2006, you should maintain your FYV
at least until 2008. It might be that you never experience problems if
you do not maintain the FYV in this time range, but some processes do
additional checks and then it can come to problems
Regards,
Rakesh

Fiscal Variant

Data in split week (week crosses between 2 months) is not desegregating correctly. to resolve the problem, we are planning to use Fiscal variant.
Is it going to be a problem, when I release the fcst to R3 and SNP? Both R3 and SNP are not using fiscal variants? We use data in daily buckets to R3 and SNP.
Desegregation of split week causes any problem, if quarterly and yearly check boxes are checked in storage bucket profile. My gut feeling, it should not cause any problem. (We are not using any quarterly or yearly time buckets). I know, its going to store the data in both the buckets and UN necessarily occupies the LC space.
Any input is greately appreciated.
thx
Jeff

Hi Jeff,
As you are using the Day Buckets in SNP, I am sure that there will be not issue in releasing to SNP though you are using FYV.
Regarding
Kumar

How to configure fiscal variant

Hi ,
Please provide me some steps or doc's related to Fiscal variant config
Krish

Hi,
The fiscal year variant contains the number of posting periods in the fiscal year and the number of special periods.
This is the link for what is fiscal year.
http://help.sap.com/saphelp_47x200/helpdata/EN/96/8b2fd543ce11d189ee0000e81ddfac/frameset.htm
This is the link for fiscalyear variant
http://help.sap.com/saphelp_47x200/helpdata/EN/08/513f9943b511d182b30000e829fbfe/frameset.htm
Tcode : ob29
Regards,
Senthil kumar.p

Maintaining Fiscal Variant Between R3 and BW

Are the fiscal variants between R3 and BW maintained automatically through business content?
If so, how do I go about making sure the fiscal variants in BW are updated with those in R3?
Thanks
CB

Hi Chad,
In RSA1 > Modeling > Source Systems, right click the R/3 source system and choose Transfer Global Settings. Here you can check mark Fiscal Year Variants and execute.
Hope this helps...

Fiscal Variant, Holidays for Time Stream IDs

While choosing the periodicities for a planning area, I have to choose a storage bucket profile and the fiscal variant. Can any one tell where and how actually to create the fiscal variant(or for that matter, fiscal calendar) by myself.
Also, please let me know how I can create a time stream ID with holidays-both regular(weekends) and special.

HI Gurucharan,
For the Fiscal year variant go to OB29 transaction in R/3 (actually should be done by FI consultant) where the fical year period is maintained like 12 months or 16 months. This can be transferred to APO.
Time stream Id is just mapping a Factory calender in it. When the forecast transferred to R/3 the forecast orders wouldn't be created on holidays.
There are standard Fiscal year variants are there. Please check.
Saravanan V

Fi posting error due to fiscal period error 1

HI SAP GURUS,
I am trying to post TR6 Challan in todays date & getting following message-
Fi posting error due to fiscal period error 1
Message no. 8I216
Diagnosis
Attempt to post the document in a period outside the current Fiscal
period setup.
Procedure
Change the posting date or Change the fiscal period prior to posting
the transaction under consideration.
please help me to resolve the issue.
CHEERS

HI
This error is due to Posting period is not open in FI check the posting period is opened for all the accounts in OB52 then post the entries
hope it will be usefull

Single Query with multiple fiscal variants / fiscal period

Experts,
Currently we have two different queries 1) for US and 2) for Mexico.
Both the queries are hard-coded with respective company codes and different fiscal variants. We have i step =1 variable, so in both query we have respective fiscal period by default in variable screen. The user can decide to run the query for current fiscal period or manually overwrite it for past few fiscal periods.
Now, we want to consolidate two queries into a single one and behind the scene depending on company code entered by user we want the query to run for default period AND we also want user to have liberty to change it for different fiscal periods (similar to istep 1 variable) which is hard coded for each query. Please advice how to proceed?
Thanks!

Hi Durgesh,
I agree with part 1- we can let user select his company code, but my challenge is pre-populate or get the default fiscal period for different company codes.
2) You can keep rest of the things as it is, because you will be populating the default period value and if user want he can select the required value manually.
(Alok) = So if user runs report in Nov'2011 = the US fiscal period is 002/2012; but for Mexico it might be 011/2011 - so is there any way where we can give this value in prompt screen and at the same time not let user remember these values...
Since with single query and without hardcoding how to determine the current fiscal period for different company codes?

Delete old Fiscal variant / Fiscal Periods / Fiscal Year from the BW

Hi
When initially Loading data we had different fiscal variant for each source system.
This was found not to be correct and after the initial load we reloaded the same data with a common fiscal variant across source systems.
Now the problem we have on hand is that we do not want the old Fiscal variant / Fiscal Periods / Fiscal Year to show up in the F4 pop up.
Is there a way to delete these old Fiscal variant / Fiscal Periods / Fiscal Year from the BW System.
regards

Hi,
Go to your infoprovider, select the required characteristic and in the Infoprovider specific properties under the F4 values for filter option, you can choose "Only values from infoprovider data".
Just check if this option is available with time characteristics or not.
Regards,
Durgesh.

Fiscal Year Variant Error

Hi All
we are getting the below error when trying to post the transaction MICN :
Fiscal year variant T2 is incorrect
Message no. F5234
However, i have checked OB29, OMSY, OB37 & OB52 - all are correctly set up...
can anyone guide me as to how I can correct this error
Thank you
Rukshana

Hi Christian
Thank you for the response...
yes I have checked all of them and none of them are giving me a solution.
SAP OSS notes too are not much of a help....
Thats why I am trying to pick someone's brain to see if they have encountered a similiar error and what they did to rectify it..
Thanks again
Rukshana

Different fiscal variant for same controlling area

Hi,
as my client requirement is having 3 company codes two having same fiscal year variant another having different fiscal year for legal requirement operating under same same county.
i have maintain all the setting for the 3 company codes but .
but when i enter to maintain controlling area OKKP.
system is throwing following error.
Differing fiscal year variants: V3 - ZP
Message no. KT297
Diagnosis
Fiscal year variant V3, controlling area SQRE, does not agree with fiscal year variant ZP, company code 3000.
The following entries must agree:
u2022 Same number of posting periods (the number of special periods may vary)
u2022 Same period limits
Procedure
Ensure that the fiscal year variants of the controlling area and the assigned company codes agree. If necessary, maintain the fiscal year variants.
Please suggest me how to proceed further in this case.
thanks
kareem

Hi Kareem
What you are doing is not correct
All comp codes under the Contrr Area must have same FYV and same Ch of accounts
1. Go to IMG and assign same FYV to the 3rd comp code
2. Go to IMG > FI (New) > Global Settings > Ledgers > Define and Activate Non-Leading Ledgers
Here, activate parallel ledger for this 3rd comp code and assign the other FYV in the parallel ledger
Also maintain the Doc No ranges for parallel ledger because your FYV will be different between Main and Parallel ledger
br, Ajay M

In OB29 which box should I flag on if I want to select my fiscal variant N6

Hello,
On BW side I want to select my fiscal year varaint as N6, so I go to tcode OB29 and which cloumn should i flag on the first one or second (year dependent or calendar year) right now none of that boxes are selected. ?
The calendar year cloumn has 5 boxes flaged on K0 to K5 what does that mean ?
Can i make the changes staright away in production?
After making the changes do i have to reload the data to get right periods for the transaction data?
Thanks in advance

fiscal year variants are usually defined on the source system. We transfer the global settings from the source system to BI for currencies, fiscalyear variants, UOM, factory calender. Go to source system, right click on ur source system - transfer global settings - fiscalyear variants - Mode - update tables.

Variant error in f-22

i post one document in f-22 document number 100000 after that this document number to assign the correspondece request in fb12 system asks document number,company code once enter request saved in f.64 i have execute this one according to the document number whther system showing error messaage
Variant ZI1 does not exist & where we create the related programme variant

thanks for your sending answer it is very helpful answer, i post one document document no: 102005 after fb12 this document is request for correspondence but the system showing defaultly the correspondence of sap19 for customer invoice how to change this one & once i am executing f.64 i had given input parameters for correspondence or company code after execute the system popup error message
Report allocatn for correspond.type SAP19 has not been fully maintained
A correspondence request SAP19 was selected for company code 1005, for which the report allocation to the correspondence type has not been maintained completely. The name of the print program and/or the name of the variant is missing in the report allocation.

Fiscal variant error

Similar Messages

Maybe you are looking for