For a company involved in a merger or acquisition, one of the first steps after completing the transaction is to ensure common financial reporting standards. When the merged business units use different fiscal years, this is critical to be aligned.

Differences in fiscal year setup can take various forms. In some cases, the difference in fiscal year setup can be related to the fiscal periods’ setup – for example, fiscal periods based on calendar months versus fiscal periods based on a 4-4-5 calendar. In other cases, the fiscal year’s start and end date may be different.

Changing the fiscal year in your SAP system can be a challenging project:

– Time dependency – as the end of the fiscal year is coming nearer, making changes to the fiscal year setup can become a time-critical project.

– Lack of experience – typically, the fiscal year setup is only rarely changed in an up and running SAP system, and both IT departments and system integrators lack experience.

– System complexity – fiscal year periods are used and maintained in various areas in your system. As a result, fiscal year changes must be done consistently between general ledger, asset accounting, logistics, controlling, connected systems, etc. Failure to do so can result in critical data inconsistencies.

– Data adjustment – some applications may have already posted data into future fiscal periods that need to be changed. Examples are applications such as revenue recognition or financial and logistics planning data.

Datavard offers standardized services and tools for making the fiscal year change in your SAP system, adjusting both the fiscal year configuration and any dependent data in the system.

To learn more about the Datavard services for changing fiscal year setup, schedule time with one of our technical experts to address your questions.

Reducing the footprint of BW on HANA systems When running a SAP Business Warehouse, one of the first-choices for integrating SAP with Big Data is NLS (Nearline Storage). NLS is a way to move data out of the primary database and store it in a more cost efficient, but slower ...
Archiving and Decommissioning
Business Warehouse
Cloud
Data Management
Datavard OutBoard
Goetz Lessmann
Goetz Lessmann
SOFFCONT1 table grows quickly in SAP landscapes and often gets into the top 10 largest tables in the system (TIP: check the list of largest tables in DB02 transaction). This table belongs to SOC3 and contains SAP Business Workplace/SAPoffice Documents attachments. The size of SOFFCONT1 depends significantly on how ...
Data Management
Avatar
Jan Meszaros
Choosing a new NLS solution As Informatica recently announced that they are discontinuing support for their ILM Nearline storage, many companies are looking for a suitable replacement. There are a lot of options to choose from – be it the in-house SAP IQ, traditional databases such as Oracle, MSSQL or ...
Archiving and Decommissioning
Business Warehouse
Data Management
Datavard OutBoard
Avatar
Jan Meszaros