We won't be going into great detail about the configuration options, however it is useful to understand the available possibilities in SAP Advanced Financial Closing. First we will looks at some general configurations available:
Country/Region Groups
Defining country/region groups for financial closing enables you to monitor the completion rate and status of financial close activities on the level of country/region groups. This is how it's done:
Company Code Groups
This was previously discussed in the Reviewing the Closing Process lesson.
In company code groups, you group company codes that can be defined by the same value for a specific grouping characteristic. You create them within one specific characteristic.
Compliance Settings
The compliance settings apply to all apps that are part of SAP Advanced Financial Closing. The following options are available:
Anonymize Names in Emails. You can specify whether you want real names to be removed from emails sent by the SAP Advanced Financial Closing notification service. The default is no.
Anonymize Completed Task Lists After. You can define a number of months as the time offset after which user names are removed from completed task lists. The default value is 18 months.
Notify User Before Task Is Due. You can arrange for email and SAP Fiori notifications to be sent to the processing user or user responsible. You define how many minutes before a task is due users are reminded about the task.
Enforce SOX Requirements. Determine whether the Sarbanes-Oxley Act (SOX) compliance applies. The default value is Yes. If the selection is set to Yes, the following rules apply:
- User responsible and processing user of a task or folder must not be the same.
- Responsible user group and processing user group of a task or folder must not be the same.
- If a user group contains only one user and the group is assigned as the responsible user group or processing user group, the user of the group must not be the same user as the one maintained for the other role. This rule is checked only during the consistency check.
Note
If you deactivate this option, no checks for compliance with the SOX requirements will be run anymore. If you activate this option again, only objects created after activating this setting will be checked for SOX requirements. To ensure SOX compliance of existing task list templates, you need to run a consistency check. Task lists that were generated before SOX compliance was required might still not fulfill the SOX requirements. However, during task approval, a check ensures that the approving user is not the same as the processing user.
Email Notification Configurations
A notification configuration assigned to a task list controls when and how processing users or users responsible are notified by email. The settings in the notification configuration apply to the task list and to all tasks in the template or task list.