This blog is a step-by-step guide which encompasses the configuration process of compliance reports where the global Fiscal Year Variant (FYV) of a company is deviating from the calendar year.

To depict this case as simple as possible, let’s take the following example:

A customer is implementing S/4HANA Cloud with the global FYV S6 which starts on July 1st and ends on June 30th of the next calendar year. Due to the required generation of monthly, quarterly and yearly reports, it was decided to activate Scope Item 1J2 “Advanced Compliance Reporting”.

When looking at the monthly reports, e.g. EC Sales List for the Netherlands, the following results are displayed:

Blog_1.png

As you can see, the Submission Due Date and Reporting Periods do not match with the Reporting Year which should start in July 2018 and end in June 2019.

To achieve a congruent result, the periodicity needs to be maintained in the configuration as follows:

Info: Please consider that the approach for the monthly, quarterly and yearly reports is very similar. To have a full overview and to avoid any confusion, the reporting intervals will be explained end-to-end. Therefore, feel free to jump directly to the required setup within this blog. 




Monthly Reports


Step 1:

At first, open SSCUI 103124 “Clean Up Reporting Tasks”. With this configuration step inconsistent tasks due to the change of the periodicity will be deleted. To run this SSCUI, it is mandatory to choose at least one Reporting Entity. If you want to narrow down this activity to a certain Report Category or Reporting Period, fill out the fields below as well. After a successful simulation in Test Mode, the tasks can be cleared in Production Mode. Do not worry in case the compliance reports are not displayed in the “Run Compliance Reports” app anymore. After few seconds they will re-appear.

Blog_2.png

 

  

Step 2:

Then switch to SSCUI 101071 “Setting Up Your Compliance Reporting”. Chose a Reporting Entity and Report Category in the Dialog Structure. After that, the FYV can be changed in the sub-structure “Set Periodicity of Report Categories”. Since the first line of the periodicity is pre-delivered by SAP, it cannot be deleted. To close it, set a “to-date” and save the change before making new entries. Then, a new line can be created either by clicking on the “New Entries” or “Copy As…” button. For our example we choose S6 in column FY Variant and take over the entries for Offset and Notify from the first line.

 

The change of the periodicity within this SSCUI does only have an impact on the “Run Compliance Reports” app. This is the reason why different periodicities can be selected in parallel for different reports and the global FYV.

 

Info: While the offset determines the submission due date in the “Run Compliance Reports” app, the notify column indicates the number of days the user receives a notification in his inbox before the offset. Further information including good examples can be found in the F1-help!

Blog_3.png



Step 3:

When comparing the following overview with the very first screenshot from the intro, a change can be observed. The Submission Due Date, the Reporting Year and Reporting Period were adapted to S6 and are shown as required.

Blog_4.png


 

Quarterly and Yearly Reports

Since the maintenance of quarterly and yearly reports require the exact same configuration steps, both intervals were merged into one chapter.

Currently, S/4HANA Cloud is not delivered with quarterly and annually FYVs which deviate from the calendar year e.g. S6. Therefore, it would not be possible to run reports in such time intervals starting from July and ending in June. The consequence is that the Submission Due Date, the Reporting Year and Reporting Period do not match:

Blog_5.png

Blog_6.png

Step 1:

The solution starts with the creation of new FYVs in SSCUI 102712 “Maintain Fiscal Year Variants”. Click on the New Entries button, enter the FYVs, the Descriptions and Posting Periods. A suggestion is presented in the following screenshots using Q6 (quarterly) and C6 (annually):

Blog_7.png

Blog_8.png

 

 

Step 2:

When diving into the sub-structure, the periods can be maintained. To keep an interval of three months starting from July, enter the last day of September, December, March and June. Consider the switch of the calendar year for the last two periods. The columns Calendar year / week and Day are updated automatically.

Blog_9.png

  

With some modification, this also applies for the annual FYV.

Blog_10.png

 

Info: From here on, the same steps are used as described for the monthly report setup. Therefore, the text barely differs, except for periodic-specific changes.

Step 3:

Please open SSCUI 103124 “Clean Up Reporting Tasks”. With this configuration step inconsistent tasks due to the change of the periodicity will be deleted. To run this SSCUI, it is mandatory to choose at least one Reporting Entity. If you want to narrow down this activity to a certain Report Category or Reporting Period, fill out the fields below as well. After a successful simulation in Test Mode, the tasks can be cleared in Production Mode.

Do not worry in case the compliance reports are not displayed in the “Run Compliance Reports” app anymore. After few seconds they will re-appear. 

 Blog_11.png

Blog_12.png

Step 4:

Then switch to SSCUI 101071 “Setting Up Your Compliance Reporting”. Chose a Reporting Entity and Report Category in the Dialog Structure. After that, the FYV can be changed in the sub-structure “Set Periodicity of Report Categories”. Since the first line of the periodicity is pre-delivered by SAP, it cannot be deleted. To close it, set a “to-date” and save the change before making new entries. Then, a new line can be created either by clicking on the “New Entries” or “Copy As…” button. For our example we choose Q6 (quarterly) and C6 (annually) in column FY Variant and take over the entries for Offset and Notify from the first line.

 

The change of the periodicity within this SSCUI does only have an impact on the “Run Compliance Reports” app. This is the reason why different periodicities can be selected in parallel for different reports and the global FYV.

 

Info: While the offset determines the submission due date in the “Run Compliance Reports” app, the notify column indicates the number of days the user receives a notification in his inbox before the offset. Further information including good examples can be found in the F1-help!

 Blog_13.png

Blog_14.png

 

Step 5:

When comparing the following overviews with the first screenshots of this section, a change can be observed. The Submission Due Date, the Reporting Year and Reporting Period were adapted to S6 and are shown as required.

Blog_15.png

Blog_16.png

 

Since the frequency to run a report can vary, the periodicity for monthly, quarterly and annually reports can be maintained in parallel. Also, please keep in mind that this approach needs to be adapted according to further FYVs deviating from the calendar year e.g. S3 (April till March).

I hope this blog helps you out in case you are facing such a situation. If you have further questions, feel free to ask them in the comments section. Feedback would be appreciated as well.

Thank you and best regards

Dennis