Dual fiscal year

Hi all,
Please let me how can i handle dual fiscal year in SAP Business One.
For Example. Our company is in India following Fiscal Year From
April to March . Where as my parent company is following the Fiscal Year from January to December.
Please let me know how can i handle in SAP Business One.
regards
Suresh S

Hi Suresh
I think your concern is reporting to the head office using their fiscal year and not your own defined in your database? You can run the Trial Balance and Profit & Loss reports for a date range, with other words from a date to a date, that is not necessarily the fiscal year (the Balance Sheet however does not allow for this). The only problem with this is that there will be journals in April that make your income & expense accounts zero and will skew the results of these reports as they will start at zero in January at the head office. I am assuming that the head office will require only a trial balance or possibly a detailed General Ledger report. You could write a query on the OJDT/JDT1 tables and use GROUP BY on G/L accounts and select the date range to generate a trial balance for the period and forward this to the head office. Alternatively you could try XL Reporter, though you might have similar limitations there.
Will you report in Local Currency or System currency (Head Office currency)? Make sure to write the query to use the correct currency amount fields.
Kind regards
Peter Juby

Similar Messages

Calendar Year & Fiscal Year

Hi All
I have a table which contains a calendar period and fiscal period. I want to use one table only, no alias to bring back all the periods in the current calendar year e.g 200701 which is January to 200712 which is December and also to bring back all periods from the current fiscal year e.g. 2007/08-01 which is April 2007 to 2007/08-12 which is March 2009 so my result set should look something like below
Calendar Period Calendar Month Fiscal Period Fiscal Month
200701          January 2007/08-01     April
200702          February 2007/08-02     May
200703          March 2007/08-03     June
200704          April 2007/08-04     July
200705          May     2007/08-05     August
200706          June      2007/08-06     Spetember
200707          July 2007/08-07 October
200708          August     2007/08-08     November
200709          September 2007/08-09 December
200710          October     2007/08-10     January
200711          November 2007/08-11     March
200712          December 2007/08-12     April
Can I restrict one table to bring back both of these?

Below is what i am using at the moment for testing before i create the table. A table has not yet been created for this yet but this is the format I was told is needed
select
'200701' as period, '200701' as quarter, 'January' as month, '2006/07-10' as fiscal_period, '2006/07-04' as fiscal_quarter
from dual
UNION
select
'200702' as period, '200701' as quarter, 'February' as month, '2006/07-11' as fiscal_period, '2006/07-04' as fiscal_quarter
from dual
UNION
select
'200703' as period, '200701' as quarter, 'March' as month, '2006/07-12' as fiscal_period, '2006/07-04' as fiscal_quarter
from dual
UNION
select
'200704' as period, '200702' as quarter, 'April' as month, '2007/08-01' as fiscal_period, '2007/08-01' as fiscal_quarter
from dual
UNION
select
'200705' as period, '200702' as quarter, 'May' as month, '2007/08-02' as fiscal_period, '2007/08-01' as fiscal_quarter
from dual
UNION
select
'200706' as period, '200702' as quarter, 'June' as month, '2007/08-03' as fiscal_period, '2007/08-01' as fiscal_quarter
from dual
UNION
select
'200707' as period, '200703' as quarter, 'July' as month, '2007/08-04' as fiscal_period, '2007/08-02' as fiscal_quarter
from dual
UNION
select
'200708' as period, '200703' as quarter, 'August' as month, '2007/08-05' as fiscal_period, '2007/08-02' as fiscal_quarter
from dual
UNION
select
'200709' as period, '200703' as quarter, 'September' as month, '2007/08-06' as fiscal_period, '2007/08-02' as fiscal_quarter
from dual
UNION
select
'200710' as period, '200704' as quarter, 'October' as month, '2007/08-07' as fiscal_period, '2007/08-03' as fiscal_quarter
from dual
UNION
select
'200711' as period, '200704' as quarter, 'November' as month, '2007/08-08' as fiscal_period, '2007/08-03' as fiscal_quarter
from dual
UNION
select
'200712' as period, '200704' as quarter, 'December' as month, '2007/08-09' as fiscal_period, '2007/08-03' as fiscal_quarter
from dual
union
select
'200801' as period, '200801' as quarter, 'January' as month, '2007/08-10' as fiscal_period, '2007/08-04' as fiscal_quarter
from dual
UNION
select
'200802' as period, '200801' as quarter, 'February' as month, '2007/08-11' as fiscal_period, '2007/08-04' as fiscal_quarter
from dual
UNION
select
'200803' as period, '200801' as quarter, 'March' as month, '2007/08-12' as fiscal_period, '2007/08-04' as fiscal_quarter
from dual
UNION
select
'200804' as period, '200802' as quarter, 'April' as month, '2008/09-01' as fiscal_period, '2008/09-01' as fiscal_quarter
from dual
UNION
select
'200805' as period, '200802' as quarter, 'May' as month, '2008/09-02' as fiscal_period, '2008/09-01' as fiscal_quarter
from dual
UNION
select
'200806' as period, '200802' as quarter, 'June' as month, '2008/09-03' as fiscal_period, '2008/09-01' as fiscal_quarter
from dual
UNION
select
'200807' as period, '200803' as quarter, 'July' as month, '2008/09-04' as fiscal_period, '2008/09-02' as fiscal_quarter
from dual
UNION
select
'200808' as period, '200803' as quarter, 'August' as month, '2008/09-05' as fiscal_period, '2008/09-02' as fiscal_quarter
from dual
UNION
select
'200809' as period, '200803' as quarter, 'September' as month, '2008/09-06' as fiscal_period, '2008/09-02' as fiscal_quarter
from dual
UNION
select
'200810' as period, '200804' as quarter, 'October' as month, '2008/09-07' as fiscal_period, '2008/09-03' as fiscal_quarter
from dual
UNION
select
'200811' as period, '200804' as quarter, 'November' as month, '2008/09-08' as fiscal_period, '2008/09-03' as fiscal_quarter
from dual

Use of Different Fiscal Year Variant-Statistical Depreciation Area Postings

An existing Company Code in SAP is going to have Fixed Assets implemented. This Company Code is setup just like the others in our SAP instance: Same Chart of Accounts, Same Fiscal Year Variant, Fixed Asset procedures, etc. For purposes of this question our company's Fiscal Year is from August 1st to July 31st. In addition, this Company Code will post Fixed Assets just like the other SAP enabled Company Codes into Book Depreciation Area 01. The company I work with is on ECC 6 but we use the Classic Ledger for Financials, and the Special Ledger is posted to but not really utilized.
For the Country Specific/Tax Reporting purposes within Fixed Asset Accounting we have created a Statistical Depreciation Area 03 (I will call it Tax) with its own Life and Depreciation Key assignments with a setting of 0 in OADB-No Posting in GL for this Fixed Asset go-live, so I think we are set there. The tricky part comes in the reporting. The country in question requires information to be generated on a Calendar Year basis, which is obviously different than the Fiscal Year outlined above. To my knowledge we would have to assign Tax Depreciation Area 03 to the Calendar Fiscal Year Variant: Financial Accounting>>Asset Accounting>>Valuation>>Fiscal Year>>Fiscal Year Variants>>Specify Other Versions on Depreciation Area Level.
The other piece of this is to get the Fixed Asset Reporting for Tax Depreciation Area 03 to work on a Calendar Year basis for the Company Code in question. When I did some research I stumbled upon the link below. In summary it says that you have to manipulate the standard Fixed Assets reports in Excel for Asset Acquisitions and Depreciation, and setup a new Retirement routine/transaction for posting into the Special Depreciation Area.
http://help.sap.com/saphelp_46c/helpdata/en/05/bc0bf3d8f811d1953e0000e82debf7/content.htm
My questions are:
1) Besides assigning a different Fiscal Year Variant for Tax Depreciation Area 03, is there anything else I need to worry about on the setup end?
2) Is the article I posted accurate when it comes to how the reporting works and the need for setting up a Calendar Year specific Asset Retirement Routine? If so, what are the configuration steps for setting up a Calendar Year specific Asset Retirement Routine?
3) Is there anything else that I need to consider for enabling Fixed Assets at an existing Company Code with different Reporting requirements for Book/Tax purposes?
Thanks in advance for all responses. I am willing to answer any other questions on this subject if needed.
Roman

Hello Rio. In our scenario, we still had to load assets in the legal entity with this issue. When we loaded the fixed asset data into SAP we did with data accurate as of December 31, 2011; which for book purposes is 5 months into our company's fiscal year, and for tax purposes is the end of the 2011 calendar year. The calendarized reporting for the tax depreciation will need to be pieced together manually using the SAP recommended methodology of combining report values, which I have pasted below.
Since this is the only SAP-enabled entity that has this scenario right now we are in wait and see mode to see if this sufficient. In the end the SAP path for Dual Calendar was too much of a risk.
I hope this helps.
Roman
Asset Acquisitions
Run the acquisitions list. Report date: 7/31/2012. Posting Date: 1/1/2012 to 7/31/2012. Export the report to MS Excel.
Run the acquisitions list. Report date: 7/31/2013. Posting Date: 8/1/2012 to 12/31/2012. Export the report to MS Excel.
Add the values of both reports together, using MS Excel.
Asset Retirements
Run the retirements list. Report date: 7/31/2012. Posting Date: 1/1/2012 to 7/31/2012. Export the report to MS Excel.
Run the retirements list. Report date: 7/31/2013. Posting Date: 8/1/2012 to 12/31/2012. Export the report to MS Excel.
Add the values of both reports together, using MS Excel.
Depreciation
Run the depreciation list. Report date: 7/31/2012. Export the report to MS Excel.
Run the depreciation list. Report date: 12/31/2011. Export the report to MS Excel.
Run the depreciation list. Report date: 12/31/2012. Export the report to MS Excel.
Using MS Excel functions, subtract the second report from the first, and then add the third report (I - II + III).

Find the fiscal year for the date

My fiscal year starts from 1st of august to july31
if i pass the period Aug-2011 need to know in which fiscal year it falls in
Expected output as 2012.
How can i write simple query

hI,
893185 wrote:
select EXTRACT (YEAR FROM ADD_MONTHS ('AUG-2011', 5)) from dual
The above is giving non numeic character. How can i write the sqlThe first argument to ADD_MONTHS is supposed to be a DATE, not a string.
Use a DATE instead of the string 'AUG-2011'. For example:
EXTRACT (YEAR FROM ADD_MONTHS ( TO_DATE ( 'AUG-2011'
                                        , 'MON-YYYY'
                     , 5
     )

Open and Close periods/Fiscal years

Dear All
We are in the process of FM-BCS implementation, we observed thre is transaction code (FMOPER) for open the Budget periods. This is working for Budget workbech (FBMM) only. But at the time of Actual Postings even period is not open in FMOPER system is allowing for actual postings.
Kindly suggest where we can control actual postings through period open/cose option in FM-BCS.
Thanks in advance
Rao

Hi Rao,
You need to be aware of all the impact of the use of PBET (Period-Based Encumbrance Tracking) before activating it in transaction OF39. This is not a simple change, it impacts all your integrated postings that come from all other areas (FI, CO, MM, SD) into FM.
You cannot use any FM update date other than the POSTING date when PBET is active.
One common error when you activate PBET is FI_E050 - Posting date/period 00/00/0000 is earlier than existing
date/period 00/00/0000.
If you want updating to take place on the delivery date, you must return profile to Fiscal Year Based (non-PBET) updating.
This step will also eliminate the error FI_E050.
Part of the basic PBET logic, aims at recording a detailed change history of every single document in FM.
For more details on this, please also refer to the program documentation and chapter Public Sector Management -> Funds Management -> Recording Actual and Commitment Data -> Period-Based Encumbrance Tracking.
The standard functionality when PBET is active is to use the system date as the FM posting date. However, you do have 3 options to overwrite this:
Document Creation:
1.- Version Management (PR/PO)
2.- FM updating date is the document posting date.
Document Change:
1.- System use FM_TRANS_DATE date as FM updatign date, if this date is not filled, system use system date as FM updating date.
If customer want to change this logic, the FM updating date is decided by one of the following three steps, in order shown.
- Version Management (PR/PO): Posting date of version
- Transaction FMOD to override the update date by user
- Activate user exit EXIT_SAPLFMFA_004 so that a popup screen is
displayed that permits entering the FM posting date, you could
manually set the date found in the document header to a later date.
- you could manually set the date found in the document header to a
later date (System date SY_DATUM).
PBET is Periodic-based encumbrance tracking and it is a function that monitors encumbrances per period, with a change record issued for each change made within a period. This function belongs to Funds Management Area (PSM-FM).
If PBET is active, system does not allow posting to a date earlier than the present date, you will receive error FI_E050 in case this is not satisfied. Follow are two comments form the code which indicate same:
"No new dates can be earlier than the original or new account assignment line items".
"Ensure that new fm update dates are not older than original date or if a change, this change must be latest date in document"
To use or not to use PBET is customer decision and this impact that the period is verified more strictly than without PBET. Maybe you should consider with your consultant if using PBET is the best solution for your business processes.
Best Regards,
Vanessa.

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

Import fixed assets in middle of fiscal year 2013

Hi,
I like to import several fixed assets in middle of fiscal year 2013. The attached file works fine but when I then look at the depreciation months, I see the depreciation for the complete year of 2013. But when I set the start depreciation date in the import file set to 2013-11-01 the import is not working anymore because of wrong calculation of lifetime.
How can I import this fixed asset with start depr date set to 2013-11-01 and only the last 2 months (Nov and Dec) need an depreciation for 2013??
And not also the previous months !!!
Thanks again.
Mark

Hi Mark,
Import FA with depreciation start date as 2014/01/01 and run the depreciation for the said two months by doing an journal entry. Depreciation is calculated for a whole year.
Isaac.

How to add FISCAL YEAR, Period and Day to cube.

hi,
I am using SD EXTRACTORS (2LIS_11_VAITM, 2LIS_11_VAKON, 2LIS_12_VCITM and 2LIS_13_VDITM) and directly updating each corresponding ODS and cube.
All the extractors only have FISCAL VARIANT has the time characteristic. So, all my ODS contains only one time char - fiscal variant and other dates (liek document created date etc. (not a time char)).
Now, I want to use fiscal period, fiscal year and fiscal day in my cube. I have added these time char in my cube.
My question:
1. how to get FISCAL YEAR, FISCAL PERIOD and FISCAL DAY get updated. Do I need to map to document created date in update rules or Do I need to use some functional module.
Pls note I am bringing only FISCAL VARIANT from R/3 into ODS and then to CUBE.
PLS REPLY.

thanks sundar..i got your point..but I have one question
All the cubes (sales, sales condition and billing) have the sales order number (VBUK-VBELN) and item number (POSNR-VBUK). But info objects used for these fields in sales cube and sales condition cube are same but for billing it is not same.
Can I combine all cubes (sales order, sales condition, billing) in muliti provider.
1. Sales order cube (from VAITM)
           Sales order number (VBUK-VBELN) -- (0DOC_NUMBER)
           Sales Item (VBUK-POSNR)              -- (0S_ORD_ITEM)
Date : Document created date (VBAK-AUDAT) -- 0DOC_DATE
2. Sales Condition cube (from VAKON)
           Sales order number (VBUK-VBELN) -- (0DOC_NUMBER)
           Sales Item (VBUK-POSNR)              -- (0S_ORD_ITEM)
Date: Document created date (VBAK-AUDAT) -- 0DOC_DATE
Key field: Netprice (VBAP-NETWR) -- 0NET_VALUE
3. Delivery Cube (from VCITM)
         Sales order number (VBUK-VBELN)   -- (0DELIV_NUMB)
         Item   (VBUK-POSNR)                         -- (0DELIV_ITEM)
Date: Delivery Date :LIKP-WADAT_IST      -- 0ACT_GI_DTE
4. Billing Cube (from VDITM)
          Sales order number (VBUK-VBELN) -- (0BILL_NUM)
          Sales Item (VBUK-POSNR)              -- (0BILL_ITEM)
Date: Billing Date: (VBRK-FKDAT)             -- (0BILL_DATE)
Key field: Net price (VBRP-NETWR)       -- 0NETVAL_INV
I want to combine above cubes. If I combine, Will I get correct data??????
Points will be assigned to every useful answer

Shortened Fiscal Year and its impact on BI back end and Bex reports

Hi All,
Our client is making some changes to the fiscal year period.
Becuase of some business requirements, we will have to shortened the fiscal year.
Can you please suggest - what are the watch points when we do this?
- what will be the impact to BI back end and Bex reports?
Thanks,
Nisha

Hello Nisha,
Since the fiscal year (Infobjects - 0FISCYEAR and/ 0FISCPER3) is compounded with fiscal year variant, therefore maintaining the correct variant in BI will automatically take care of showing the data correctly.
So there are two things to be maintained in BI:
1) To see that the variant definition.
2) If you need to display the text of the fiscal periods, then the correct texts.
Let me know if you need more clarifications.
Regards,
Shweta
Edited by: Shweta Kesarwani on Jan 8, 2010 11:10 AM

Fiscal year period quarter in purchasing cube

*Dear friends,*
*I want to make one query on the basis of fiscal year Qurterly . So please what is infobject in purchasing data cube is useful for making this query. Please guide me*
*Thanks and Regards*
*Anil*

Hi,
due to the fact that you dont want to use the quarter of the calendar year, you should build up an appropriate one and add it to the cube. Also you should fill it by formula or routine.

Mid Month Calculation for Year dependent fiscal year

Hi All,
We are in middle of AA implementation .How can we configure mid month in year dependent fiscal year .System doesn't allow to put mid month date for year dependent fiscal year.
If we copy co.code from best practice co.code BP01 system updates date this table in back round.
But we are not copying from BP01.
Any one has configure this for year dependent please input.
Thanks,

Hi,
this function is not possible, you have to use a fiscal year variant with 24 real periods instead.
Check the IMG documentation concerning "Use of Half Months in the Company Code":
- When you specify the use of half periods in the definition of an asset company code, half periods are automatically specified in all other company codes that use this fiscal year version.
- You cannot use half periods with non-calendar fiscal months.
- You cannot take back the use of half periods once the specification has been made. It is noted internally by the system in the asset master records.
Regards,
Markus

Reversal of Asset accounting document in different fiscal years

Hello All,
i have one query where the user has scrapped the assets through T code ABAVN in the month Dec 2009 with doc date of Nov 30th 2009. Now he realised that the posting was wrong and he wants to reverse it in 1st of Jan 2010. Now system is giving an error "Reversal in different fiscal year is not possible" with the message AA487.
we are using SAP ECC 5.0 and i got SAP 1393737 for this and it is mention that there is a program error and needs to implement the program corrections.
Please can any one suggest me, is that correct approach or should i need to follow the another work around to resolve this issue.
Thanks in advance.
Regards,
Venkat

as per your scenario it is pure program error, so don't look for alternative solution. implement note and try to reverse the document.

FI-AA Impact on changing the year dependent fiscal year period from 445 to 435

Dear Friends,
May I have your comment on the impact of below change
Currently using Year Dependent fiscal year variant K5 and period end closing is *445
future we want to use the same fiscal year dependent variant K5 , however the period end closing will be *435
*445 Periods - 1st month 4th sat, 2nd month 4th sat, 3rd month 5th sat will be the closing periods
similarly for the rest of the months in a year
*435 Periods - 1st month 4th month, 2nd month 3rd sat, 3rd month 5th sat will be the closing periods
similarly for the rest of the months in a year
Impact on Asset Module and other modules will be a great help
Regards
SB

Hi Sanjai,
SAP do not recommend to change a Fiscal Year Variant that has already
been assigned to a company code and has already some postings. This
will may create database inconsistencies
Please check the following SAP notes which will give you an
idea of some adverse effects that may happen as a result of a change
based on the modules/components you have implemented in your system.
427920     Analysis program for fiscal year conversion
210861     Changing fiscal year variant in production system
193713     SAPF070: Change of fiscal year variant
672255     Shortened fiscal year/changing fiscal periods
The change of the fiscal year or the change of the fiscal periods
has an effect in many modules, for example, in FI, FI-AA, FI-SL, FI-LC,
EC-CS, IM, CO, EC-PCA, MM, PP, SD, PS, PM.
Corresponding risks (for example, data inconsistency, system standstill)
can arise from incorrect changes to the fiscal year or from incorrect
changes to the fiscal periods in a live SAP system.
You can refer to the following wiki page also:
http://wiki.sdn.sap.com/wiki/x/jYXrCw
I hope you find this information helpful.
Regards,
Jose

FI Impact on changing the year dependent fiscal year period from 445 to 435

Dear Friends,
May I have your comments on the impact of below change
Currently using year dependent fiscal year variant K5 and Period closing is *445
Future we want to use the same year dependent fiscal year variant K5 and period end closing is *435
*445 Periods - 1st month 4th sat, 2nd month 4th sat, 3rd month 5th sat will be the closing periods
similarly for the rest of the months in a year.
*435 Periods - 1st month 4th sat, 2nd month 3rd sat, 3rd month 5th sat will be the closing periods.
similarly for the rest of the months in a year.
Impact from FI perspective and other modules would be of great help
Regards,
SB

Hi Sanjai,
SAP do not recommend to change a Fiscal Year Variant that has already
been assigned to a company code and has already some postings. This
will may create database inconsistencies
Please check the following SAP notes which will give you an
idea of some adverse effects that may happen as a result of a change
based on the modules/components you have implemented in your system.
427920     Analysis program for fiscal year conversion
210861     Changing fiscal year variant in production system
193713     SAPF070: Change of fiscal year variant
672255     Shortened fiscal year/changing fiscal periods
The change of the fiscal year or the change of the fiscal periods
has an effect in many modules, for example, in FI, FI-AA, FI-SL, FI-LC,
EC-CS, IM, CO, EC-PCA, MM, PP, SD, PS, PM.
Corresponding risks (for example, data inconsistency, system standstill)
can arise from incorrect changes to the fiscal year or from incorrect
changes to the fiscal periods in a live SAP system.
You can refer to the following wiki page also:
http://wiki.sdn.sap.com/wiki/x/jYXrCw
I hope you find this information helpful.
Regards,
Jose

Impact on changing the year dependent fiscal year period from 445 to 435

Dear Friends,
May I have your comments on the impact of below change
Currently using Year Dependent fiscal year variant K5 and period end closing is *445
Future we want to use the same year dependent fiscal year variant K5, however the period end closing will be *435.
*445 Periods - 1st month 4th sat, 2nd Month 4th Sat & 3rd Month 5th sat will be the closing periods
similarily for the rest of the months in a year.
*435 Periods - 1st month 4th sat, 2nd Month 3rd sat & 3rd Month 5th sat will be the closing periods
similarly for the rest of the months in a year.
Regards,
SB

Hi Sanjai,
SAP do not recommend to change a Fiscal Year Variant that has already
been assigned to a company code and has already some postings. This
will may create database inconsistencies
Please check the following SAP notes which will give you an
idea of some adverse effects that may happen as a result of a change
based on the modules/components you have implemented in your system.
427920     Analysis program for fiscal year conversion
210861     Changing fiscal year variant in production system
193713     SAPF070: Change of fiscal year variant
672255     Shortened fiscal year/changing fiscal periods
The change of the fiscal year or the change of the fiscal periods
has an effect in many modules, for example, in FI, FI-AA, FI-SL, FI-LC,
EC-CS, IM, CO, EC-PCA, MM, PP, SD, PS, PM.
Corresponding risks (for example, data inconsistency, system standstill)
can arise from incorrect changes to the fiscal year or from incorrect
changes to the fiscal periods in a live SAP system.
You can refer to the following wiki page also:
http://wiki.sdn.sap.com/wiki/x/jYXrCw
I hope you find this information helpful.
Regards,
Jose

Dual fiscal year

Similar Messages

Maybe you are looking for