Update from September 2018 to explain the new option “change fiscal year”:
Your company got aquired by a company with a deferred calendar year? Usually this is the time, when you might need to think of changing the fiscal year variant.
What other option do you have now?
You have in principle two options:
- Re-Migration
Creating a new company with the new fiscal year variant and migrate the data of the existing tenant to the new company (in short: re-implementation of the company)
or - Service to replace fiscal year variant
Contact the SAP Cloud Service Center and check if there is the possibility to replace the current fiscal year variant with the new fiscal year variant with the chargeable service “Fiscal Year Variant change”. This is usually the best choice, if the requirement is to quickly move to the new fiscal year variant, but all accounting settings can stay as they are (no addition set of books required, no other account principle, …)
For option 2 we require the new target fiscal year variant. The approach is that fiscal year is merged with the feature of “shortened fiscal years“, e.g. if you move from Calendar Year to April – March, then you need a shortened fiscal year to “bridge” the Jan – March period. The years are in sequence, which means 2018 the shortened year after 2018 is 2019, and then 2020 starts …
For option 1 you have the option to set up the company in the same or a fresh tenant. If you stay in the same tenant, then you can reuse the company independent data and need to follow this steps to achieve this:
- Request a new test tenant
- Create a new company in the new tenant in parallel to the old company
Advantage: master data can be re-used, at least the company independent part;
historical data are still available - Create the new Set of Books
Fiscal year variant is a key field for the Set of Books definition, that why it cannot be changed.
The Chart of Accounts, etc. can be reused. - Assign the new company to the new Set of Books
You cannot assign a subsequent Set of Books to a company after the first posting.
But even if it would be technically okay, after my evaluations I do not think, it is a good approach for a new fiscal year variant. - Extract all open transactions and migrate them to the new Set of Books
Similar to a standard migration, you need to migrate open items. For open POs and SO you need to check if you need to migrate them, re-using is no option.
For data download you can use reports and OWLs. In addition SAP offers services to extract data with tools.
Before the upload- Please check especially with respect to Fixed Assets, that the right values are used. Also the Fixed Asset IDs cannot be re-used.
- Ensure that the old bank accounts data are not valid any longer (otherwise bank statement processing will determine the “old” bank accounts and clear old items)
- Add the new company specific data to the master data for the new company.
- All employees have to be transfered to the new company
unfortunately “fire and re-hire” is the only option.
Recommendation: define a new determination reason, e.g. “Reorg” to see the transfers for the re-org. - Update User Access Rights:
You have to ensure, that the employees can only create and edit data for the new company. So check the access rights of all your employees.
For self services the new cost centers will be defaulted. - Last but not least: Delimit the old company by maintaining the end date
The validity of an organizational unit is considered when creating new data. So you will get an error when creating e.g. POs for the old company.
Feedback is welcome.
Marlene Katzschner
SAP Cloud Service Center
Did someone followed this protocol and if so could you pls. share your experience. That would be great.
Update October 2017:
SAP Cloud Service Center offers a service, which under certain conditions allows the change from one fiscal year variant to another fiscal year variant. If you are interested in such change, please raise an incident or drop an email providing the following information:
Remarks:
e.g.If you change from “Jan – Dec” to “July – June” on Juli 1st 2017, then Jan – June will be Fiscal Year 2017, July – June 2018 will be 2018.
e.g. If you have posted a document for the example above with posting date 13.7. the period old was 7/2017. The new will be 1/2018. Such change is not possible.
Marlene Katzschner – We were recently acquired and will need to switch from a fiscal year to a calendar year. We have just under 550 employees in byD and a large amount of engineering and manufacturing data. Before I submitting an incident I need to learn more about this process. Would you be the correct person to get in touch with directly? I need to plan this internal project out and in order to do so I need more information about the process.
Jennifer Knaus
jknaus@aurora.aero
We are going trough the same process as well now. Jen did you compete your transition?
Dear Diederik,
if you are interested in adjusting your fiscal year variant, please get in contact with me either using an incident or an email to the above email address.
I have done the change of the fiscal year variant already for a few customers w/o issues and would recommend to see if this works for you. For the remigration please keep in mind that this is a larger project with the same issues as every other migration (e.g. open POs have to be migrated, open items to be migrated, etc.)
Best regards
Marlene
Hi Marlene，
Do customers need to migrate the data from new test tenant to production tenant after all implementation and test are done in new test tenant?
Thanks,
Eda
Hi Eda
for the described case of migration to a new company in the same tenant you proceed the same way as any other migration.
Best regards.
Marlene