SAP Audit Management - Public User Guide - 1.5 SP00
SAP Audit Management - Public User Guide - 1.5 SP00
2022-03-14
1 What's New in SAP Audit Management for SAP S/4HANA 1.5 SP00. . . . . . . . . . . . . . . . . . . . . . 7
5 Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.1 Organizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Create Organization Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Create Organization Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Configure Organization Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Create Organizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Upload Organizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
6 Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.1 Audit Type, Category, and Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Audit Type Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.2 Audit Universe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Auditable Item Lifecycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Create Auditable Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
7 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.1 Audit Announcement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Create Announcement Letters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Announcement Letter Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Announcement Letter Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
7.2 Risk Assessment in Audit Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
7.3 Design and Review Audit Execution Work Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
7.4 Work Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Configure Work Program Structure using Scope Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Create Work Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Upload Work Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Copy Work Program from Other Audits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Audit Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
8 Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.1 Perform Audit Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Perform Business Rule Ad Hoc Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Perform Detection Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
8.2 Evaluate Auditee's Responses to Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Audit Scoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.3 Evaluate Control Effectiveness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
8.4 Work Done. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
8.5 Work Package Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Submit Work Packages for Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Review Work Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
9 Follow-Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9.1 Track Ongoing Audits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129
9.2 Historical Audits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
9.3 Track Open Findings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
9.4 Historical Findings and Reopen Findings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
9.5 Track Open Action Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
9.6 Historical Action Plans and Reopen Action Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
10 Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
10.1 Prepare Audit Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
10.2 Review Audit Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
10.3 Issue Audit Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
10.4 Close Audits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Release 1.5 SP00 of SAP Assurance and Compliance Software for SAP S/4HANA introduces the following new
and changed features described below:
Available
Solution Title Description Version Type as of Action
SAP Audit New SAP 1.5 SP00 introduces the following SAP Fiori 1.5 SP00 New 2022-03-1 Info only
Managem Fiori apps apps: 4
ent for
● Organizations
SAP S/4H
● Dimensions
ANA
● Resource Management
● My Profile
● My Work Packages
● Review Work Packages
SAP Audit Depre The following old non-Fiori apps are deprecated: 1.5 SP00 Deleted 2022-03-1 Info only
cated
Managem 4
apps ● Organizations
ent for
● Dimensions
SAP S/4H
● Resource Management
ANA
● My Profile
SAP Audit Notifica Notification center on the Launchpad is avail 1.5 SP00 New 2022-03-1 Info only
able
Managem tion 4
ent for In addition to emails, notifications can also be
SAP S/4H delivered via the notification center on the SAP
ANA Audit Management Launchpad.
SAP Audit Data Mi Enable customers who are moving to SAP Audit 1.5 SP00 New 2022-03-1 Info only
gration Management to mass migrate data to the SAP
Managem 4
Audit Management system.
ent for
SAP S/4H
ANA
SAP Audit Organiza The new Fiori app Organizations comes with 1.5 SP00 New 2022-03-1 Info only
tions new capabilities including:
Managem 4
ent for ● You can see the risks, controls, and audita
SAP S/4H ble items related to an organization and its
ANA audit history, audit findings, and action
plans.
● You can create multiple organization hier
archies to maintain the organization data
of your own company and other entities,
such as your vendors and partners.
● You can use organization types to catego
rize individual organizations.
● You can use drag and drop to change the
position of an organization across a hierar
chy.
● You can remove organizations.
● Custom defined fields are allowed.
SAP Audit Dimen The new Fiori app Dimensions comes with new 1.5 SP00 New 2022-03-1 Info only
sions
Managem capabilities including: 4
ent for
● Dimensions can be structured into hierar
SAP S/4H
chies.
ANA
You can use drag and drop to change the
position of a dimension across a hierarchy.
● The KRIs of a dimension are inherited form
the assigned risks.
● Show the related auditable items and audit
history.
SAP Audit Risk View-dependent risk analysis 1.5 SP00 Changed 2022-03-1 Info only
Managem In the view-dependent risk analysis mode, the 4
ent for risk analysis documented in a view doesn't over
SAP S/4H write the analysis in other views.
ANA
See View-dependent and Version-based Risk
Analysis [page 52].
SAP Audit Import Manually assign organizations to imported 1.5 SP00 Changed 2022-03-1 Info only
master risks and controls
Managem 4
data
ent for When risks and controls are imported, their or
SAP S/4H ganization assignment is also imported. Previ
ANA ously, you cannot change the organization as
signment. Now you are allowed to manually as
sign organizations in case you don't want to im
port organizations.
SAP Audit Where- When you try to remove an organization, dimen 1.5 SP00 New 2022-03-1 Info only
used sion, risk, or control that is still being used, an
Managem 4
check error box pops up with a Show Where Used List
ent for
button.
SAP S/4H
ANA When you try to delete a working paper that is
still being used, an error box pops up with a
Show Where Referenced List button.
SAP Audit Historical When you access an outdated organization, di 1.5 SP00 New 2022-03-1 Info only
version in mension, risk, control, or working paper from a
Managem 4
dicator historical audit, the message "This version is not
ent for
the latest" is shown.
SAP S/4H
ANA
SAP Audit Resources The new Fiori app Resources Management 1.5 SP00 New 2022-03-1 Info only
Manage
Managem comes with new capabilities including: 4
ment
ent for
● Group audit staff into teams.
SAP S/4H
● Create new audits.
ANA
● Check the unassigned audits.
SAP Audit My Profile The new Fiori app My Profile comes with new ca 1.5 SP00 New 2022-03-1 Info only
Managem pabilities including: 4
ent for
● Upload profile photos.
SAP S/4H
● More personal information.
ANA
● Calendar with more views.
● Specify the time period for substitution.
SAP Audit Audit type New audit type 1.5 SP00 New 2022-03-1 Info only
Managem The new audit type Partner is introduced. 4
ent for
Map organization types to audit types
SAP S/4H
ANA You can restrict the organization types that are
relevant to a certain audit type.
SAP Audit Copy au You can create a new audit by copying an exist 1.5 SP00 New 2022-03-1 Info only
dits ing one.
Managem 4
ent for See Copy Audits [page 86].
SAP S/4H
ANA
SAP Audit Work pro Copy function enhancement 1.5 SP00 Changed 2022-03-1 Info only
gram
Managem The filters Audit Status, Audit Type, Audit 4
ent for Group , and Audit Category are provided to help
SAP S/4H you find audits more easily when copying work
ANA programs.
SAP Audit Risk As Perform risk assessment in the audit prepara 1.5 SP00 New 2022-03-1 Info only
sessment tion phase to obtain more understanding of the
Managem 4
in Audit auditee and their environment as the basis of
ent for
Prepara your audit.
SAP S/4H tion Phase
ANA See Preparation [page 91].
SAP Audit Go to The buttons Go to previous procedure and Go to 1.5 SP00 New 2022-03-1 Info only
next/ next procedure are available on the screen of a
Managem 4
previous procedure, which help you easily navigate
ent for
procedure across the procedures within a work package.
SAP S/4H
ANA
SAP Audit Test Pro Attach links to steps 1.5 SP00 New 2022-03-1 Info only
cedures
Managem When creating a test procedure, you can attach 4
ent for links to a step. For example, for a step of in
SAP S/4H specting sales documents, you can attach the
ANA link to the sales system where the sales orders
can be found.
SAP Audit Business Use parameters for ad hoc queries 1.5 SP00 Changed 2022-03-1 Info only
rule pro
Managem You can define the output fields, the filter crite 4
cedure
ent for ria, and the deficiency criteria for a business
SAP S/4H rule ad hoc query.
ANA
See Business Rule Procedure [page 107].
SAP Audit Detection Create findings 1.5 SP00 Changed 2022-03-1 Info only
procedure
Managem You can create findings as results of detection 4
ent for procedures.
SAP S/4H
Reopen detection procedure
ANA
You can reopen a completed detection proce
dure.
SAP Audit Submit You can enable a review process for the com 1.5 SP00 New 2022-03-1 Info only
work pleted work packages.
Managem 4
package
ent for See Work Package Review [page 114].
for review
SAP S/4H
ANA
SAP Audit Finding Make Ranking optional 1.5 SP00 Changed 2022-03-1 Info only
Managem You can make field Ranking optional using Cus 4
ent for tomizing activity Maintain Field Attributes.
SAP S/4H
Check if Executive Responsible is assigned
ANA
A new quality checkpoint "Executive Responsi
ble must be assigned" is available.
Reference
SAP Audit Action Change deadline 1.5 SP00 Changed 2022-03-1 Info only
plan
Managem The buttons Extend Deadline and Advance 4
ent for Deadline are provided for changing the deadline
SAP S/4H of an action plan.
ANA
Sub action plans inherit information from pa
rent action plans
SAP Audit Work Rich text available 1.5 SP00 Changed 2022-03-1 Info only
Done
Managem You can use a rich text editor to create work 4
Notes
ent for done notes.
SAP S/4H
ANA
SAP Audit Working Reply to review notes 1.5 SP00 New 2022-03-1 Info only
Paper
Managem You can add replies to a review note of a working 4
ent for paper.
SAP S/4H
See Reply to Review Notes [page 140].
ANA
Activity history
SAP Audit Customiz Customizing activity Maintain E-mail 1.5 SP00 Changed 2022-03-1 Info only
ing activ Notifications for Audit Activities has been re
Managem 4
ity renam named Maintain Notifications for Audit
ent for
ing Activities.
SAP S/4H
ANA
SAP Audit Analytics CDS views are provided for reporting. 1.5 SP00 Changed 2022-03-1 Info only
Managem See Analytics and Reporting. 4
ent for
SAP S/4H Note
ANA
SAP Audit Management no longer provides
HANA views for analytics.
SAP Audit Role New role: Partner 1.5 SP00 New 2022-03-1 Info only
Managem A new application role Partner and the corre 4
ent for sponding PFCG role SAP_GRCAUD_PARTNER
SAP S/4H are introduced.
ANA
New role: External Auditor
SAP Audit Field Set Hide obsolete field choices 1.5 SP00 New 2022-03-1 Info only
Managem tings For choice fields such as Audit Type, you can 4
ent for hide choices that are no longer needed so they
SAP S/4H are not available for selection.
ANA
See Hide Field Choices.
Technical Details
The application component for SAP Audit Management for SAP S/4HANA is GRC-AUD.
Related Information
What's New in SAP Assurance and Compliance Software for SAP S/4HANA 1.5 SP00
What's New in SAP Assurance and Compliance Software for SAP S/4HANA
SAP Audit Management for SAP S/4HANA [page 14]
SAP Audit Management for SAP S/4HANA is a solution for building audit plans, preparing audits, and analyzing
relevant results.
SAP Audit Management for SAP S/4HANA provides an end-to-end audit management solution that can be
used to build audit plans, prepare audits, analyze relevant information, document result, form an audit opinion,
communicate results, and monitor progress. The key features include the following:
● Full mobile-enablement and easy access from multiple devices and platforms
● Full coverage of the audit roadmap; including planning, preparation, execution, report, and follow-up
● Flexible Audit Universe that serves as a single source for audits and monitors audit requests globally
● Integration with third-party systems such as SAP Business Integrity Screening and SAP Risk Management
● Powerful working paper management that allows you to create audit documents via drag-and-drop, single-
click access to the documents, and management review
● Global monitoring of findings and following up on the progress of actions
● Powerful search function that helps you find the target information easily
● Clear and intuitive user interface design that improves user experience and boosts efficiency
In SAP Audit Management for SAP S/4HANA, the auditing process is divided into five phases: planning,
preparation, execution, reporting, and follow-up. Different audit tasks are performed in different phases.
The following figure illustrates the workflow of an audit. Note that the roles only serve as an example of a typical
auditing scenario in an organization. You may have different roles for each action depending on your
authorization settings.
The audit announcement letter approval process is an optional feature depending on the audit status
schema configuration.
This documentation is generally structured in accordance with the above five phases. It includes the following
sections:
For more information about the terminology used, see SAP Glossary.
For more information about corrections made to the product assistance after shipment, see SAP Note
3050167 .
Several settings need to be adjusted in order to set up SAP Audit Management for SAP S/4HANA.
In the following sections you will find the information you need to set up the application, including
authorizations, transactions, language settings, and browser settings:
Additional Information
For more technical information, see the Installation Guide, and the Security Guide on the SAP Help Portal at
http://help.sap.com/audit_s4.
3.1 Home
The home page is the starting point of the application. It is based on the SAP Fiori launchpad and can be called
using transaction /UI2/FLP.
The launchpad opens a home page that contains predefined content, divided into groups. Each group contains
tiles that represent business applications. Clicking or tapping a tile launches the underlying application.
● Personalization
The group My Home is, by default, the first group on your home page. Other groups may also be visible to
you, as defined by your administrator.
You can personalize the application home page by selecting Edit Home Page. Once you do, you can add
groups and tiles. As well, you can rearrange existing tiles by dragging them to a new location in a group or
moving them to another group.
Choose Settings to display the user account, or to change the appearance or language and regional
settings of your screen.
Choose App Finder to search the catalogs for all available tiles.
● Search
With the search, you can find predefined objects, such as detection strategies, alerts, events and
documents in alerts.
shares warrants None Finds results that contain both the word “shares” and the word “warrants”.
shares OR warrants OR Finds results that contain either the word “shares” or the word “warrants”.
shares‑warrants ‑ Finds results that contain the word “shares” but not the word “warrants”.
warr* * Finds results containing words that start with “warr”, for example “warrants”,
“warranty”, and “warranted”.
“with best regards” “” Finds results that contain the exact phrase “with best regards”.
Note
If you can't find the expected results try again using *, for example *12345 or *john*.
In SAP Audit Management, the following objects can be searched using the search from the SAP Fiori
launchpad:
● Auditable items
● Audits
● Findings and actions
● Working papers, reports, announcement letters, and attachments
● Risks and controls (latest version)
● Dimensions
Available Tiles
More Information
For more information about the SAP Fiori launchpad, see Using the Launchpad and Personalizing the
Launchpad on the SAP Help Portal.
App
Audit Universe
Controls
Dimensions
Initiate Audit
My Action Plans
My Findings
My Ongoing Audits
My Work Packages
My Recent Objects
Organizations
Prepare Audits
Record Time
Resource Management
Risk Register
Note
Transactions can be used in the back-end for SAP Audit Management for SAP S/4HANA.
The following transactions are available in the SAP Audit Management menu:
Auditable Items
Data Protection
Remove User Names ACS_DP_ANONYMIZATION Use this function to remove user names for data that is
not going to be archived.
Display Data Protection ACS_DP_LOG Use this function to display the application log for data
Logs protection activities.
SRALMANAGER
Read Access Logging Use this function to monitor and log read access to sensi
Manager tive data.
SAP Audit Management for SAP S/4HANA has two types of roles: application roles and PFCG roles.
Application Roles
Application roles are the roles you see on the user interface, for example, audit manager, audit lead, and
auditor. You can assign these roles to users when you create an audit object.
An application role is only meaningful when it is mapped to a PFCG role, because all user authorizations and
menu access derive from the relevant PFCG roles. You can define whether an application role is mandatory, and
whether it can be mapped to multiple PFCG roles. You can also specify the identity providers for different
application roles in Customizing.
The following application roles are delivered by SAP Audit Management for SAP S/4HANA:
ACT_RESP Action Responsible Person The person who is responsible for the
actions proposed in the audit finding.
ADTB_REQ Auditable Item: Requested By The person who requested the audita
ble item in the audit universe.
ADTB_RES Auditable Item: Responsible Person The person who is responsible for en
suring that the item is audited.
CAE Chief Audit Executive The chief audit executive (CAE) pre
pares the audit plan for the organization
based on risk assessments, overlooks
the auditing process, ensures that the
audit plan is carried out, and communi
cates the audit results to the senior
management and the board.
PFCG Roles
PFCG roles are back-end roles that provide authorizations and access to menu items. PFCG roles are used in
the following two ways:
● PFCG roles can be assigned to users. When you assign a PFCG role to a user, the user can have the
authorizations and accesses that are defined in the PFCG role.
● PFCG roles can also be mapped to application roles. When a PFCG role is mapped to an application role,
only users who have the same PFCG role can be assigned to this application role during the creation of an
audit object.
Example
PFCG role SAP_GRCAUD_AUDIT_MANAGER is mapped to application role AUD_MGR. When you create an
audit, only the users with the same PFCG role assigned can be selected as the audit manager.
If another PFCG role is also mapped to AUD_MGR, then users with this role assigned can also be
selected.
Access to the apps on the SAP Audit Management Launchpad are granted by the Fiori roles.
In SAP Audit Management, the following standard PFCG roles and corresponding Fiori roles are provided:
Executive
ager
ministrator
Manager
Note
This role is designed for auditors
and audit leads to
Note
The above PFCG roles contain all authorizations and menu entries that are available for SAP Audit
Management. This list should only be used as a template. For use in a production system, you must create
your custom roles based on these roles, and modify the authorizations and menu entries according to your
requirements.
To enable users to send e-mail notifications of audit activities, the following background processing
authorization must be maintained for the relevant PFCG roles:
S_BTCH_ADM BTCADMIN Y
JOBGROUP ''
Alternatively, you can also make a copy of standard role SAP_GRCAUD_FRAUD_INTEGRATION and assign it to
your user. This role already contains the above required authorization.
For more information about PFCG roles, see the Security Guide at http://help.sap.com/audit_s4.
More Information
For more information about how to maintain application roles and role mappings, see the Customizing
activities and their documents under PFCG SAP Audit Management Basic Settings Role Settings .
For more information about supported browsers, see Browser and Platform Support.
The browser cache is deleted automatically and periodically. However, if you want, you can run the
report /UI5/APP_INDEX_CALCULATE to perform an immediate refresh.
When you start the application, the language that is displayed depends on the following:
● If you select the language on the logon screen, your selection is transferred to the back end with the URL
parameter.
● If you use single sign-on (SSO), the language of the browser settings is transferred to the back end.
Note
The language settings defined in the User Maintenance (transaction SU01) in the back end has no influence
on the application.
If a text is not available in the logon language, the corresponding text in a fallback language is displayed. Usually
the fallback language is English, but in some functions, the “secondary language” defined in the application
server is used. To achieve uniform behavior, SAP recommends using English as the secondary language.
3.6 Notifications
Notifications can be delivered in the following two forms. You can enable either or both of them.
● Emails
See Email Notification [page 27].
● Notification Center on the SAP Audit Management Fiori Launchpad
See Enable Notification Center on the Launchpad [page 28].
Procedure
Configure the generation of URLs in email notifications when the frontend and backend are deployed in
different servers.
Context
SAP Audit Management sends email notifications that contain links. For example, when an audit is initiated, an
email notification containing the link to the audit is sent.
When the frontend and the backend are deployed in different servers, the host and the client in the URLs of the
links must point to the frontend.
Procedure
1. Go to transaction SE16.
2. Enter the table name HTTPURLLOC.
3. Choose Create Entries.
4. Choose New Entries.
For the field APPLICATN, please enter SAPGRCAM<Your frontend client>. For example, SAPGRCAM110.
By default, e-mail addresses are case sensitive in SAP Audit Management. For example, if you maintain the e-
mail address [email protected] in your user's master data, you cannot send back documents to the system using
[email protected] even if your e-mail client does not differentiate the two addresses.
You can turn off the case-sensitivity setting in Customizing activity Maintain Case Sensitivity Setting.
Send notifications via the Notification Center on the SAP Audit Management Launchpad.
Procedure
The application offers an optional integration of SAP Jam, the SAP tool for collaborative work and coordination.
For help with using SAP Jam for collaboration, see http://help.sap.com/jam .
SAP Jam must be added to the SAP Fiori launchpad. If you do not find SAP Jam in your Home screen, then see
Adding SAP Jam to the SAP Fiori Launchpad in the Installation and Configuration Guide at http://help.sap.com/
audit_s4.
If you plan to move to SAP Audit Management, you can migrate your data to the SAP Audit Management
system using the predefined spreadsheet templates.
● Audits
● Findings
● Action Plans
You have to migrate audits first, and then findings and then action plans. This is because findings are
dependent on audits and action plans are dependent on findings.
Migrate Audits
To migrate audits,
Sheet Description
Auditable Items With the Auditable Items sheet, you can assign auditable
items to audits.
You can only select from the auditable items listed in the
Auditable Item List sheet.
Auditable Item List The Auditable Item List sheet lists all of the auditable
People With the People sheet, you can assign people to audits by
assigning users to roles.
You can only select from the users and roles listed in the
Roles and Users List sheet.
Roles and Users List The Roles and Users List sheet lists all the users in your
system and the roles for the object type Audit.
You can only select from the organizations listed in the Or
ganization List sheet.
Organization List The Organization List sheet lists all the organizations you
have maintained in the Organizations app in SAP Audit
Management. You cannot create new organizations using
this sheet.
Working Paper Categories The Working Paper Categories sheet lists all the working
paper categories you have defined.
Working Paper With the Working Paper sheet, you can upload audit work
ing papers. To do so, enter the local path to the file to be
uploaded in the Working Paper File Path field.
4. After you have maintained your audits in the spreadsheet, go to Customizing activity Migrate Audits to
upload the spreadsheet.
You are required to fill in the Scope Name. An empty work program will be automatically generated for each
migrated audit. The scope name you entered will be used as the name of the nodes in the work program.
Migrate Findings
To migrate findings,
Sheet Description
Findings In this sheet, you choose audits by ID and then enter find
ings per audit.
You can only select from the organizations listed in the Or
ganization List sheet.
Organization List The Organization List sheet lists all the organizations you
have maintained in the Organizations app in SAP Audit
Management. You cannot create new organizations using
this sheet.
People With the People sheet, you can assign people to findings
by assigning users to roles.
You can only select from the users and roles listed in the
Roles and Users List sheet.
Roles and Users List The Roles and Users List sheet lists all the users in your
system and the roles for the object type Finding.
4. After you have maintained your findings in the spreadsheet, go to Customizing activity Migrate Findings to
upload the spreadsheet.
Sheet Description
People With the People sheet, you can assign people to action
plans by assigning users to roles.
You can only select from the users and roles listed in the
Roles and Users List sheet.
Roles and Users List The Roles and Users List sheet lists all the users in your
system and the roles for the object type Action.
Attachments With this sheet, you can upload attachments for your ac
tion plans. To do so, enter the local path to the file to be
uploaded in the File Path field.
4. After you have maintained your action plans in the spreadsheet, go to Customizing activity Migrate Action
Plans to upload the spreadsheet.
SAP Audit Management provides the functionality for users to upload data using standard templates.
For example, you can download a template, maintain data offline for controls, risks, dimensions, auditable
items, and work programs, and upload it to the system. These standard templates are delivered by SAP and are
designed to work with most spreadsheet tools. However, there are a few tips that you need to know before you
jump in and maintain the data.
Note
SAP Audit Management enables you to use different workflows depending on audit types.
The workflow is determined by the so-called status schema. A status schema defines:
To configure workflows,
Prerequisites
Sync the audit staff member list in SAP Audit Management with your identity providers in Customizing activity
Sync Audit Staff with Users from Identity Provider.
Key Features
● Group audit staff into teams and use team calendar to track schedules.
See Create Teams and Use Team Calendar [page 34].
● Maintain skills and qualifications.
See Maintain List of Skills and Qualifications [page 35].
● Classify audit staff into job groups and job levels and set daily pay rates to track audit cost.
See Audit Staff Classification [page 36].
● Audit staff can set up their profile.
See Set Up Profile [page 37].
● Track the time your audit staff spend on audits.
See Time Tracking [page 39].
In the Resource Management app, you can group audit staff into teams and use team calendar to track the
schedules of a group of people and manage projects.
For example, you can group people with similar working roles or job levels into a team, and when you schedule a
new project, you can check their calendar to decide who is available for this project.
Create Teams
To create a team,
The team calendar in Resource Management shows who is working on which audit and when.
Maintain a list of audit-relevant skills and qualifications and so when your auditors set up their profile, they can
specify which of the skills and qualifications they possess. When resourcing audit projects, you can select
auditors by skills and qualifications.
Skills
To maintain a skill list, use Customizing activity Maintain Skills for Audit Staff.
Example
IT ● Data analytics
● IT security and infrastructure knowledge
Qualifications
To maintain a qualification list, use Customizing activity Maintain Qualifications for Audit Staff.
Use job groupings and job levels to classify your audit staff.
In Customizing activity Maintain Day Rates and Job Levels for Auditors, you can
Note
Day rate is the amount of money paid for a single working day. Staff wages are calculated based on
their day rates and recorded working hours, which will then be added to the actual cost of audits.
Follow the steps below to assign your audit staff to job groups and identify their job levels.
Note
You need to first maintain a file template for scenario STAFF_LVL in Customizing activity Maintain
Templates for File Generation. You can copy the sample file template STF_LVL_UP from client 000.
1. Go to transaction GRCAUD_UPD_STF_LVL.
2. Download the spreadsheet template that lists your audit staff.
3. In the Staff Level ID column of the template, choose a job group and a job level for each staff member.
4. Go back to transaction GRCAUD_UPD_STF_LVL and upload the spreadsheet.
Procedure
Procedure
You can designate another user as your substitute so that they can perform your tasks.
Note
It is suggested you designate an user who has the same role or permissions as yours as your Substitute. If
you are an audit manager and designate an auditor as your Substitute, that Substitute may not be able to
perform your tasks because he or she doesn't have the audit manager permissions.
Designate a substitute
To designate a substitute,
You can have only one substitute for a certain time period.
Dismiss a substitute
Your substitute is automatically dismissed when the substitution end date is reached.
SAP Audit Management enables you to track the time your auditors spend on audits and other activities.
Activity Types
You need to define the allowed activity types for time recording, such as Audit, Annual Leave, Sick Leave, and
Training. To define activity types, use Customizing activity Maintain Activity Types.
In Customizing activity Define Daily Working Hours, you can set the standard daily working hours and a
maximum daily working hour limit.
Record time
Staff can record the time they spend on activities. The time recorded for audit activities are added to the actual
effort and used to calculate the actual cost of audits.
Staff can record the hours that they spend on audits and other activities.
Procedure
If the number is smaller than the standard daily working hours, the selected dates will be marked as
Insufficient. If the number is greater than the standard daily working hours but smaller than the maximum
daily working hours, the selected dates will be marked as Overtime.
6. Choose Apply to save
Results
Each audit has an Actual Effort field, the value of which is automatically generated by combining the work hours
entered by all the involved auditing staff for that audit.
The Actual Effort field is editable by default. To prevent its value from being changed manually, we recommend
that you set the field ACTUAL_EFFORT in the Customizing activity Maintain Field Attributes by Status Schema
as read-only.
In SAP Audit Management, master data refers to organizations, risks, controls, and dimensions.
SAP Audit Management allows you to create master data, upload master data using spreadsheets, and import
from SAP Process Control or SAP Risk Management.
You can establish linkage between master data, such as between risks and controls.
5.1 Organizations
You can maintain the organization data of your company, customers, vendors, and other entities in SAP Audit
Management and use them for auditing purpose.
For example, you can link risks and controls to organizations. When planning risk-based audits, you can select
the relevant organizations for audits.
Basic Concepts
Organization Hierarchy
An organization hierarchy can be used to represent the hierarchical structure of an entity, such as your
company, or used as a catalog of organizations serving the same purpose for your company, such as your
vendors.
Organization
● Root Organization
A root organization is one without a parent organization.
● Child Organization
A child organization is one with a parent organization.
Organization Type
You can use organization types to categorize organizations. It's mandatory to specify which organization type is
allowed in a certain organization hierarchy.
Organization Group
You can use organization groups to control the authorizations to create, change, display, and delete
organizations.
You can create organization hierarchies in Customizing activity Define Organization Hierarchies.
● Internal
● Supplier
● Partner
You can create organization types in Customizing activity Define Organization Types.
● Internal
● Supplier
● Partner
You can map organization types to organization hierarchies in Customizing activity Define Organization
Hierarchies.
By mapping organization types to organization hierarchies, you specify which organization type is allowed in a
certain organization hierarchy. Only one organization type is allowed for an organization hierarchy
Example
If you map the organization type Internal to the organization hierarchy Internal, then only organizations of the
type Internal are allowed in the organization hierarchy Internal.
Use organization groups to control users' authorization to create, update, display, and delete specific
organizations.
Procedure
Assign the Display, Create, Change, and/or Delete authorization for organization groups to PFCG roles via
the authorization object ACS_ORG, and then the roles can display, create, change, and/or delete
organizations in the organization groups.
4. Assign users to PFCG roles.
Prerequisites
You have authorizations for the organization group in which you want to create the new organization. See
Configure Organization Groups [page 43].
Field Description
After you have created an organization, you can click on it to go to its detail page, where you can edit and
see its information, including the risks, controls, auditable items, audit history and so on.
Prerequisites
You have authorizations for the organization groups to which you want to upload the new organizations. See
Configure Organization Groups [page 43].
Context
Field Description
Organization Group The group of child organizations must be the same with
their parents.
4. In the Organizations app, select an organization hierarchy and then choose Mass Upload Upload to
upload the spreadsheet.
The Risk Register app is the repository of the risks in your organization, which is essential for developing risk-
based audit plans.
Key Features
● Use different views to examine risks from different perspectives, such as internal audit and risk
management.
See Views for Risks [page 46].
● Create risks individually
See Create Risks [page 48].
● Upload risks in bulk using a spreadsheet
See Upload Risks [page 49].
● Document risk analysis
See Risk Analysis [page 50].
● Use key risk indicators to monitor changes in risk exposure level and contribute to the early warning signs.
See Create Key Risk Indicators for Risks [page 52].
● Understand a risk more clearly by breaking it down to underlying risks.
The Risk Register app enables you to use different views to examine risks from different perspectives.
Pre-defined Views
Risk Register comes with two predefined views: Internal Audit and Risk Management.
● Internal Audit
This view is intended for the risks that you want to focus your audit on. Only risks in this view can be
selected for audits.
● Risk Management
This view can be used to store the risks imported from the SAP Process Control or SAP Risk Management
system.
● You can only create and edit risks in the Internal Audit view.
● Risks can be imported from one view to another. See Import Risks Between Views [page 47].
● You can create your own views. See Create Views for Risks and Controls [page 71].
If your SAP Process Control or SAP Risk Management is integrated with SAP Audit Management, you can base
your internal audit on the risks stored in SAP Process Control or SAP Risk Management.
Import risks from one view to another in the Risk Register app.
Context
The following procedure describes the steps to import individual risks from one view to another. You can use
the program GRCAUD_IMPORT and the Connector LOCAL to import all risks from Risk Management view to
Internal Audit view.
Procedure
1. In Risk Register, select the view to which you want to import risks.
2. Choose Import.
3. In the drop-down box, select the view from which you want to import risks.
4. Select the risks you want to import.
Risk Type
You can use risk types to indicate on which level a risk occurs, such as the enterprise level and the operational
level.
Risk Category
You can use risk categories to indicate the areas where risks occur, such as financial risks and IT risks.
A risk category can be broken down to child risk categories. For example, financial risks may have the child
categories: credit risks, liquidity risks and so on.
Create a risk.
Procedure
Field Description
4. Choose Save.
Next Steps
Document the risk analysis, key risk indicators, underlying risks, and controls.
Procedure
Sheet Description
You can check the Controls List sheet for the available
controls.
Organizations list This sheet lists all the available organizations. You cannot
add new organizations in this sheet.
Controls list This sheet lists all the available controls. You cannot add
new controls in this sheet.
5. In the Risk Register app, select the Internal Audit view, and choose Mass Upload Upload to upload
the spreadsheet.
The risks entered in the spreadsheet are uploaded to the Internal Audit view.
Next Steps
In the Risk Register app, document the risk analysis, key risk indicators, and underlying risks for the uploaded
risks.
In the Risk Register app, you can document the following information of a risk:
● You need to configure the likelihood, impact, and risk level scales first.
See Configure Likelihood, Impact, and Risk Levels [page 51].
● When a risk is imported from SAP Risk Management, its analysis is also be imported.
Context
You can create analysis multiple times. The analysis history is shown. You can't delete the anlysis.
Procedure
Configure rating scales for evaluation of the likelihood level, impact level, and risk level of risks.
Likelihood Level
You can configure the likelihood level scale in Customizing activity Maintain Likelihood Levels.
● Rare
● Unlikely
● Possible
● Likely
● Certain
You can use the Green, Yellow, and Red colors to represent the levels.
Impact Level
You can configure the impact level scale in Customizing activity Maintain Impact Levels.
● Insignificant
● Minor
● Moderate
● Major
● Catastrophic
You can use the Green, Yellow, and Red colors to represent the levels.
Risk Level
You can configure the risk level scale in Customizing activity Maintain Risk Levels.
● High
● Medium
● Low
You can use the Green, Yellow, and Red colors to represent the levels.
Two risk analysis sync modes are available for risks that exist in multiple views: the view-dependent mode and
the version-based mode.
● View-dependent
The analysis in a view will not overwrite that in other views until you import the risk from the view to others.
For example, create a new analysis for a risk in the Internal Audit view. The analysis will not be synced to the
Risk Management view until you import the risk from the Internal Audit view to Risk Management view.
● Version-based
When the views have the same version of a risk, the analysis in a view will overwrite that in other views.
For example, when the Internal Audit view and the Risk Management view has the same version of a risk,
you create a new analysis in the Internal Audit view, and then the analysis will also be synced to the Risk
Management view.
To switch the mode, use Customizing activity Enable View-Dependent Risk Analysis.
Create key risk indicators (KRIs) for a risk and record the KRI values at a specific point in time.
Prerequisites
Set the maximum KRI value in Customizing activity Set Max Risk Score. The limit applies to all KRIs.
Procedure
1. Go to the Risk Register app and select the Internal Audit view.
2. Select the risk.
3. Go to the Key Risk Indicators section.
4. Choose Create.
5. Enter the following information for the KRI:
Field Description
KRIs are editable. For example, you can manually update their values when there are changes.
You can understand a risk more clearly by breaking it down to more specific risks, which are referred to as the
underlying risks in SAP Audit Management.
Prerequisites
The underlying risks must already be documented in Risk Register Internal Audit .
Procedure
1. Go to the Risk Register app and select the Internal Audit view.
2. Select the risk.
3. Go to Underlying Risks section.
4. Choose Assign.
5. Select risks.
Note
Those risks that already have a parent risk or will cause circular dependency are not available for
selection.
Add controls to a risk so when the risk is selected for auditing, you can identify the controls that need to be
tested.
Prerequisites
The controls are already documented in the Internal Audit view in the Controls app.
Procedure
1. Go to the Risk Register app and select the Internal Audit view.
2. Select the risk.
3. Go to the Controls section.
4. Choose Assign.
5. Select controls.
Results
After you add a control to a risk, the risk will also be displayed for the control in the Controls app.
You can remove risks from Risk Register if it's no longer needed.
Prerequisites
Procedure
1. In Risk Register, select the view from which the risk was removed.
2. Choose Import.
3. In the drop-down, choose Removed.
The risks that were removed from the view are shown.
4. Select the risk you want to restore.
Results
The risk goes back to the view from which it was removed.
5.3 Controls
Key Features
● Use different views to examine controls from different perspectives, such as internal audit and risk
management
The Controls app enables you to use different views to examine controls from different perspectives.
Pre-defined Views
The Controls app comes with two predefined views: Internal Audit and Risk Management.
● Internal Audit
This view is intended for the controls that you want to focus your audits on. Only controls in this view can
be added to risks and selected for audits.
● Risk Management
This view can be used to store the controls imported from the SAP Process Control or SAP Risk
Management system.
● You can only create and update controls in the Internal Audit view.
● Controls can be imported from one view to another. See Import Controls Between Views [page 57].
● You can create your own views. See Create Views for Risks and Controls [page 71].
If your SAP Process Control or SAP Risk Management is integrated with SAP Audit Management, you can audit
the internal controls stored in SAP Process Control or SAP Risk Management.
Context
The following procedure describes the steps to import individual controls from one view to another. In addition,
you can use the program GRCAUD_IMPORT and the Connector LOCAL to import all controls from Risk
Management view to Internal Audit view.
Procedure
1. In the Controls app, select the view to which you want to import controls.
2. Choose Import.
3. In the drop-down box, select the view from which you want to import controls.
4. Select the controls you want to import.
The attribute Control Category is used to group controls according to their area and level.
You can define control categories in Customizing activity Maintain Control Attribute Values.
You can define control nature options in Customizing activity Maintain Control Attribute Values.
SAP Audit Management provides the following predefined control nature options:
● Adjustment
You can define control automation options in Customizing activity Maintain Control Attribute Values.
SAP Audit Management delivers the following predefined control automation options:
● Automated
● Semi-Automated
● Manual
You can define control significance options in Customizing activity Maintain Control Attribute Values.
SAP Audit Management delivers the following predefined control significance options:
● Key Control
● Standard Control
Key controls are those of which the effectiveness has material impact on the achievement of your
organization’s objectives, and standard controls have less material impact.
Create a control.
Procedure
Field Description
Control Significance
Control Automation
Control Nature
5. Choose Save.
Procedure
Sheet Description
Organizations list This sheet lists all the organizations for your reference.
You cannot add new organizations in this sheet.
5. In the Controls app, select the Internal Audit view, and choose Mass Upload Upload to upload the
spreadsheet.
The controls entered in the spreadsheet are uploaded to the Internal Audit view.
Prerequisites
The risks are already documented in the Internal Audit view in the Risk Register app.
Procedure
Results
After you add a risk to a control, the control will also be displayed for the risk in Risk Register.
You can design a rating scale for evaluating the effectiveness of controls.
To design the rating scale, use Customizing activity Maintain Control Effectiveness Settings.
● Effective
● Partially Effective
● Ineffective
5.4 Dimensions
Using different dimensions enables you to understand the risks in your organization and conduct audit through
different lenses.
Dimensions can be business processes, product lines, legal entities, IT systems, regulations, and so on.
Associating risks with the dimensions enabling a multi-dimensional view of your internal audit activity. For
example, you can focus your audit on the risks in certain business processes, or answer questions like how
many critical audit findings are related to an IT system, or understand what coverage an audit plan provides for
a legal entity.
Key Features
● Identify the dimension types you need. Example dimension types are business process, plant, and IT
system.
See Create Dimension Types [page 62].
● Document the dimensions under a type.
Hierarchical structure is allowed.
○ Root dimension
A root dimension is one without a parent dimension.
○ Child dimension
You can create dimension types in Customizing activity Maintain Dimension Types.
● Function
● Process
● Site
Create a dimension.
Procedure
Field Description
Context
You can only upload dimensions of the same type together at a time.
Procedure
3. In the Dimensions app, select a dimension type and then choose Mass Upload Upload to upload the
spreadsheet.
Results
The dimensions entered in the spreadsheet are uploaded to the selected dimension type.
You can assign a risk to a dimension to indicate that they are associated.
Prerequisites
The risks are already documented in the Internal Audit view in the Risk Register app.
Results
When risks are assigned to a dimension, the KRIs of the risks are also assigned. The Highest Risk Score of a
dimension is the highest KRI value among these risks.
5.5 Import Master Data from SAP Process Control and SAP
Risk Management
You can import master data from SAP Process Control or SAP Risk Management.
Introduction
● Organizations
● Risks
● Controls
It's recommended that you import in the order Organizations Risks Controls .
Note
The assignment relationship between objects can also be imported, such as assignment of controls to
risks. However, if controls have never been imported yet when you import risks, the assignment of controls
to risks cannot be imported. To solve this issue, you can import risks again after you have imported
controls.
See:
Field Description
Source System Type The type of the source system, e.g. SAP Risks Management
or SAP Process Control.
Source System The exact system or server from which the object is im
ported, namely the connector you use for importing.
Fulfill the prerequisites to import master data from SAP Process Control or SAP Risk Management.
● Create a connector for importing master data in the Customizing activity Set Up Connectors.
● Map values for the fields, such as the likelihood level of risks and effectiveness ratings of controls, between
SAP Audit Management and SAP Process Control or SAP Risk Management in Customizing activity Map
Field Values.
● Make sure the following authorization are assigned to your role via the authorization object AUD_VIEW:
ACTVT 16 (Execute)
AUD_VIEW View ID
BO_SERVICE Execute
● Implement the SAP Note 2952423 to import the risk category and underlying risks.
Prerequisites
Procedure
Results
● Organizations are imported to the Organizations app and stored in the specified organization hierarchy. You
can see the source information of imported organizations.
● The ID of an organization used in SAP Audit Management is the same as in the source system.
Prerequisites
Object Attributes
Risks ● Name
● Description
● Risk Type
● Risk Category
● Validity
● Organization
● Likelihood Level
● Risk Level
● Impact Level
● Underlying risks
● Controls
Procedure
Note
If you want to test the import function, you can try import a small number of risks, such as 10 risks. To
do so, enter the number in the Package Size field.
Results
● Risks are imported to Risk Register and stored in the specified target view. You can see the source
information of imported risks.
● An ID is assigned to each risk when it is imported the first time, which is used to identify it in SAP Audit
Management.
● If a risk has been imported before, it will be updated with the latest information from the source system.
Prerequisites
Context
Object Attributes
Controls ● Name
● Description
● Validity
● Organization
● Category
● Significance
● Automation
● Nature
● Risks
● Test Steps
● Test History
○ Effectiveness
○ Test Date
○ Comments
Procedure
Note
If you want to test the import function, you can try import a small number of controls, such as 10
controls. To do so, enter the number in the Package Size field.
Results
● Risks are imported to Controls and stored in the specified target view. You can see the source information
of imported controls.
● An ID is assigned to each control when it is imported the first time, which is used to identify it in SAP Audit
Management.
● If a control has been imported before, it will be updated with the latest information from the source system.
The log provides detailed information about the executed import jobs.
Procedure
1. Go to transaction SLG1.
2. Enter GRCAUD in the field Object.
3. Enter IMPORT in the field Subobject.
4. Choose Execute.
To keep the master data up-to-date with the source systems, you can schedule regular import jobs in
Customizing activity Schedule Jobs for Importing Tasks.
When the import job detects that the source object of an organization, risk, or control in the source system is
delimited, the organization, risk, or control will be removed from SAP Audit management.
Set Threshold
You can use thresholds to prevent unwanted removal of objects caused by technical errors.
When technical errors occur, such as connection errors, the import jobs may not be able to correctly identify
some objects in source systems and as a result, determine those objects as delimited. In this kind of situation,
the delimitation percentage detected by import jobs is usually high.
When there are thresholds in place, if the import jobs detect that the percentage of delimited objects is lower
than the threshold, the job will be executed and delimited objects will be removed. If the percentage exceeds
the threshold, the job will not be executed.
You can set thresholds in Customizing activity Master Data Delimitation.
You can allow the organizational structure changes in a source system to be imported into SAP Audit
Management to keep the data in the two systems consistent.
Note
You can switch on and off the import of changes in Customizing activity Enable Organization Structure Update.
You can enable the manual assignment of organizations to import risks and controls.
When risks and controls are imported, their organization assignment is also imported. By default, the
Organizations field in an imported risk or control is ready-only and so you cannot manually assign organizations
to imported risks and controls.
If an organization is imported from SAP Process Control or SAP Risk Management, you can click on the Source
Object link to go to the source system from which it is imported.
Organizations are shared by SAP Process Control and SAP Risk Management. You can use Customizing activity
Configure Navigation Path for Org to choose the application to which the source object links redirect.
You can create views for risks and controls in Customizing activity Maintain Views for Risks and Controls
However, you can only create and edit the risks and controls in the Interal Auditview.
For more information on the authorization to create and access the views, see the documentation for
authorization object AUD_VIEW.
During this phase, you identify the focus areas of audit and arrange resources for the planned audits.
Audit Type
● Assurance
● Consulting
● Partner
In Customizing activity Define Audit Types, you can create audit types and configure settings for audit types.
See Audit Type Configuration Settings [page 73]
Audit Category
● Corporate Audit
● Environment, Health, and Safety Audit
You can create audit categories in Customizing activity Define Audit Categories.
Audit Group
Audit groups can be used to control the access to auditable items and audits.
In Customizing activity Define Audit Types, you can configure the following settings for an audit type:
Configuration Description
Scope Schema Choose a scope schema for audit preparation work pro
grams.
Organization Type Choose the organization types that are relevant to the audit
type.
Add Risks from Risk Register Make it possible to manually select risks for audits.
Assign Dimensions to Audit Directly Make it possible to manually select dimensions for audits.
Disable Automatic Risk Assignment By default, when an auditable item is assigned to an audit,
the risks in the auditable item will also be automatically as
signed to the audit. You can disable the automatic assign
ment of risks and make it possible to assign risks manually.
Assign Organizations to Audits Directly By default, the organizations you can assigned to an audit
are restricted to those assigned to the auditable items in the
audit. You can remove the restriction.
Force Same Group for Auditable Items You can set the restriction that to assign auditable items to
an audit, the auditable items must be in the same audit
group with the audit.
Auditable items are also known as auditable entities, units, or areas. An auditable item can be a process,
activity, project, product line, or any entity that can be audited.
Before working with auditable items, get yourself familiar with the auditable item life cycle. See Auditable Item
Lifecycle [page 74].
Key Features
After an auditable item is created, it needs to be released in order to be assigned to audits. If you update an
auditable item after releasing it, you need to release again to make the changes come into effect.
Note
The review step can be skipped so that the auditable items can be released directly. To do so, see Release
Auditable Items Directly below.
Release Timestamp
The Release Timestamp of an auditable item shows the person who last released it and the date and time when
it was last released. Release Timestamp is not displayed if the auditable item has never been released.
If an auditable item is assigned to an audit or an audit plan, you can tell if the currently assigned version is the
latest one by its life cycle status.
Status Description
Outdated This auditable item has a released update. You need to re
fresh it to get its latest version.
To do so,
1. Go to transaction PFCG.
2. Choose the role SAP_GRCAUD_AUDIT_MANAGER.
3. Find the authorization object AUD_ITEMS and deselect the option I1: Submit.
Procedure
Field Description
Tags Use tags to classify the auditable item and make it easier
to find. Already existing tags are suggested based on the
characters you type in. You can also type new tags.
4. In the Source section, provide the background information of the auditable item.
Field Description
Requested by The person who requested that the auditable item be added to the au
dit universe.
Source More background information, such as the reason for requesting this
auditable item.
5. In the Risk section, rate the overall risk of the auditable item.
○ Risk Level
○ Impact Level
○ Likelihood Level
○ Risk Score
The overall risk rating of auditable items can help you determine the priority when scoping audits.
6. Estimate the effort needed for auditing this auditable item:
Estimated Effort for Business An estimation of the required person days from line of
businesses.
Estimated Effort for IT An estimation of the required person days from IT.
7. Save.
8. Specify the organizations related to the auditable item.
a. Go to the Organizations section.
b. Choose Assign.
c. Select organizations.
9. Specify the risks in the auditable item.
a. Go to the Risks section.
b. Choose Assign.
c. Select risks.
10. Assign dimensions to the auditable item.
a. Go to the Dimensions section.
b. Choose Assign.
c. Select dimensions.
Next Steps
Upload new auditable items in bulk to Audit Universe using a spreadsheet template.
Procedure
Auditable Items In this sheet, you can enter the following information of
auditable items:
○ Title
○ Description
○ Organizations
You can check the Organizations List sheet for the
available organizations.
○ Audit Group
○ Requested By
○ Requested On
○ Source
○ Risk Level
○ Impact Level
○ Likelihood Level
○ Risk Score
○ Estimated Effort for Business
○ Estimated Effort for IT
○ Responsible Person
Dimension List This sheet lists all the dimensions for your reference. You
cannot add new dimensions in this sheet.
Risk List This sheet lists all the risks for your reference. You cannot
add new risks in this sheet.
Organization List This sheet lists all the organizations for your reference.
You cannot add new organizations in this sheet.
3. Go to Audit Universe, and choose Mass Upload Upload to upload the spreadsheet.
The auditable items entered in the spreadsheet are uploaded to Audit Universe.
Next Steps
You can delete an auditable item that has never been released.
Procedure
You can delete auditable items that have never been released in bulk.
Procedure
1. Log on to the SAP Audit Managemen backend system. Choose a client other than the production client.
Note
You can display the role of a client – production or some other role – by choosing SAP Menu Tools
Administration Administration Client Administration Client Maintenance . The Client role field
in Details shows whether a client is a production client.
2. Choose SAP Audit Management Tools Delete Auditable Items , or enter transaction
GRCAUD_DEL_AUD_ITEM (Report for deletion of Auditable Items) in the command field.
3. Use the selection screen to choose the auditable items that you want to delete.
4. Select Execute to run the transaction.
The transaction reports how many auditable items have been selected for deletion.
5. Confirm the deletion.
When the deletion is done, a message reports how many of the selected auditable items have been
deleted. Any auditable items that could not be deleted remain unchanged in the database.
Procedure
Closing an auditable item is considered as a change to the auditable item. The change has to be released to
come into effect.
Results
Closed auditable items remain in the system. You can reopen a closed auditable item if it is needed for audits
again.
Procedure
Reopening an auditable item is considered as a change to the auditable item. The change has to be
released to come into effect.
An audit plan helps you plan a series of audits for selected risks and auditable items based on the available
resources.
If you want to carry forward the unfinished work in an audit plan to the next audit cycle, you can copy the audit
plan.
● You can only copy a released audit plan, and there can be only one copy at a time. All the items in the plan
will be copied.
● The copy is a Draft. You can edit it.
● The copy uses the same name but has a different ID.
You can close a released audit plan by archiving it. An archived audit plan can no longer be reopened.
● If a released audit plan doesn't have a copy, you can archive it manually by clicking the Archive button.
● If a released audit plan has a copy, you can't manually archive it. It is automatically archived when the copy
is released.
Procedure
Field Description
Planned Effort The effort needed for the plan, which is denominated in person work
days.
4. Choose OK.
The newly created audit plan is a draft. You can see the following read-only fields:
Budget
Field Description
Total Estimated Cost from Audits The estimated cost of the audits included in the audit plan
combined.
Total Actual Cost from Audits The actual cost of the audits included in the audit plan
combined.
Effort
Field Description
Estimated Effort for Business An estimation of required person days for line of businesses, which is
aggregated from the auditable items assigned to the audit plan.
Estimated Effort for IT An estimation of required person days for IT personnel, which is ag
gregated from the auditable items assigned to the audit plan.
Total Estimated Effort from Audits The estimated effort of the audits included in the audit plan combined.
Total Actual Effort from Audits The actual effort of the audits included in the audit plan combined.
Only those risks documented in Risk Register Internal Audit view can be added.
6. Add auditable items. You have two ways to do so:
Note
When you add an auditable item to a plan, the risks of the auditable item can also be automatically
added to the plan. To enable this function, go to the view GRCAUD_V_ATRKFAD and activate the
Customizing item AUD_AUTO_RISK_FADTBL.
Y stands for the total number of the organizations assigned to the auditable item, and X for the
number of the selected organizations.
c. In the popup, choose Edit.
d. Select organizations.
e. Save.
8. Select the dimensions to be audited.
a. Go to the Auditable Items section.
b. In the column Dimensions, click on the number X/Y.
Y stands for the total number of the dimensions assigned to the auditable item, and X for the number
of the selected dimensions.
c. In the popup, choose Edit.
d. Select dimensions.
e. Save.
Procedure
Field Description
Planned Time Period The planned start and end date of the audit.
Tags You can add tags to the audit to make it easier to find.
5. Save.
Next Steps
Procedure
Results
The auditable items in the audits are automatically added to the audit plan.
Procedure
Field Description
Planned Time Period The planned start and end date of the audit.
Tags You can add tags to the audit to make it easier to find.
4. Save.
5. Go to Auditable Items section to add auditable items to the audit.
6. Go to Risks section to add the risks that need to be audited.
7. Go to Organizations section to add the organizations that need to be audited.
8. Go to Dimensions section to add the dimensions that need to be audited.
Next Steps
Procedure
Options:
○ People
Results
The copy is named Copy of <Name of the Original Audit>. The Copied From field indicates the origin of the copy
as well as when and by whom the copy is created.
You can create and assign audits in the Resource Management app, where you can check the availability of your
auditors against the team calendar.
Procedure
Note
Audits are unassigned when the required roles of Audit Team are not assigned.
Field Description
Planned Time Period The planned start and end date of the audit.
Tags You can add tags to the audit to make it easier to find.
6. Save.
Procedure
Option Description
Stakeholder ○ CAE
○ Executive Responsible
5. Save.
Initiate an audit.
Prerequisites
Procedure
The status of the audit changes to Initiated. The audit enters the preparation phase and it moves to the
Prepare Audits app.
Prerequisites
Prerequisites
Procedure
Results
The status of the audit changes to Canceled. It moves to the Display Historical Audits app and is read-only.
The audit preparation may include the following tasks, but not all of them are mandatory.
Inform auditee of the audit objectives, scopes, and other information through an announcement letter.
Key Features
Procedure
Note
Use the Customizing activity Maintain Templates for Generating Announcement Letters to predefine
templates. The default PDF template is delivered in English. If you want to generate the announcement
letter in other languages, you need to first create a translated version of text object
GRCAUD_ANN_LETTER_NEXT_STEPS in that language in transaction SO10.
Results
To enable the review process, configure the status schema for object AUDIT. You can refer to the predefined
status schema DFLT_ANN.
The following actions and statuses are relevant for the review process:
Actions Statuses
Procedure
Option Description
● Configure the status schema for object AUDIT. You can refer to the predefined status schema DFLT_ANN.
The following action and status are relevant:
Action Status
● Configure the announcement letter recipients in Customizing activity Maintain Notifications for Audit
Activities.
Action DISTRIBUTE_AUDIT_ANNOUNCEMENT
Procedure
SAP Audit Management enables you to perform risk assessment in the audit preparation phase.
Prerequisites
Note
To enable risk assessment for an audit type, the following prerequisites must be fulfilled.
● The action START_RISK_ASSESSMENT must be included in the status schema for object AUDIT. The
predefined status schema DFLT_RA (AUDIT) is an example that includes the action.
● The status change from New to In Process must be included in the status schema for object SCOPE. The
predefined status schema DFLT_RA (SCOPE) is an example that includes the action.
● Configure a scope schema for risk assessment work programs.
Note
New work packages can be added after risk assessment is started and manually set to In Process .
Note
Review is optional. To enable or disable the review process, see Work Package Review [page 114].
You can create a work program as a hierarchy to break down your audit work into smaller tasks.
The number of levels in a work program is configurable. See Configure Work Program Structure using Scope
Schema [page 96].
Work Package
The lowest level in a work program is referred to as Work Package for the purpose of this help document,
regardless of how many levels the work program actually contains.
● Risks to be audited
● Controls to be audited
● Audit procedures to be performed
You can configure scope schemas in Customizing activity Define Scope Schema for Work Programs and then
apply scope schemas to audit types in Customizing activity Define Audit Types.
Procedure
Note
Only those controls assigned to the risks added in the previous step can be selected.
12. Create audit procedures.
Note
Procedure
Option Description
Preparation Work Program Template A blank template for audit preparation work program. To
create an audit preparation work program from scratch,
choose this option.
Execution Work Program Template A blank template for audit execution work program. To
create an audit execution work program from scratch,
choose this option.
Current Preparation Work Program To update an existing audit preparation work program,
choose this option.
Current Execution Work Program To update an existing audit execution work program,
choose this option.
Note
Next Steps
You can't assign risks and controls to work packages and audit procedures in the spreadsheets. You have to go
to the Prepare Audits app to do so.
Prerequisites
You can only copy from an audit with the same scope schema and allowed procedure types.
Procedure
Option Description
Extend Add the copied work program to the original work pro
gram.
Replace Replace the original work program with the copied work
program
Results
The preparation and execution work programs are both copied, if any.
SAP Audit Management enables you to develop the following audit procedures:
● Test Procedures
Specify a sequence of steps to perform, such as the inspection and observation steps.
● Question Procedures
Design the inquiry questions and evaluate the auditee based on the responses obtained.
● Business Rule Procedures
Execute the business rules defined in SAP Process Control.
● Detection Procedures
Use the detection strategies defined in SAP Business Integrity Screening.
For example, for a step of inspecting sales documents, you can attach the link to the sales system where the
sales orders can be found.
To enable the linking function, go to Customizing activity Use Links in Test Procedures, where you can define
link categories, link addresses and link texts. Only the links defined here can be attached to the steps in test
procedures.
Procedure
Field Description
Planned Time Period The intended start and due date for performing the test
procedure.
Person Responsible The person responsible for performing the test procedure.
4. Choose Save.
5. Go to the Steps section to specify the steps in the test procedure.
a. Choose Add.
b. Enter the name and description of the step.
c. Attach a link, if needed.
Procedure
1. Select the Test Procedures sheet in the work program spreadsheet template .
2. Choose a work package.
3. Enter the following information of test procedures. A row presents a test procedure.
○ Title
○ Description
○ Planned Start Date
○ Planned End Date
4. Open the Test Steps sheet.
5. Choose a test procedure to enter the steps in the procedure.
Procedure
You can copy the test steps from the assigned controls to a test procedure if the controls are imported from
SAP Process Control and have a test plan.
Procedure
You can only select from the controls that are assigned to the test procedure.
In the preparation phase, you use question procedures to design the questions to ask of the auditee. After
inquiry, you can document and evaluate the auditees' responses to the questions.
You can use a rating scale to evaluate auditee's responses to the inquiries.
A rating includes a text description and a numeric value. The numerical values will be used for calculating
question scores.
Compliant 10
Moderate Risk 5
High Risk 2
You can use Customizing activity Define Question Ratings to design audit type-based rating scales. When you
create a question procedure, a rating scale is automatically assigned to the question procedure according to
the type of the audit.
The score of a question procedure is calculated by multiplying the rating and the weighting.
The score of an audit is calculated by summing up the scores of all the question procedures in the audit. For
more information, see Audit Scoring [page 112].
Procedure
Field Description
Note
The rating scale is not shown when you create a question procedure. It is only shown in the audit
execution phase.
Procedure
○ Title
○ Description
○ Weight
With a detection procedure, you can use the detection and investigation capabilities provided by SAP Business
Integrity Screening to find irregularities in business data.
If a detection strategy finds irregularities and generates alert items, then these items populate a working paper
that is added to the work package. From the working paper, you can use the investigative and management
tools of SAP Business Integrity Screening to analyze each irregularity.
Detection strategies for use in detection procedures have these special features:
● Only detection strategies that have been specially marked for use in SAP Audit Management may be used
in detection procedures. These strategies may not be used by SAP Business Integrity Screening for
detection.
This feature ensures that an audit detection strategy produces alert items only in the context of an audit.
● You maintain audit detection strategies using the normal editing tools of SAP Business Integrity Screening.
You designate a detection strategy for use in auditing by setting the special Audit strategies (technical key
AUDIT in Customizing) investigation reason when you define the strategy.
● An audit detection strategy may be assigned to only a single detection procedure at a time. If a detection
strategy is assigned to a task, then it is removed automatically from the list of strategies in the input help.
● Audit detection strategies are allowed to produce duplicate alerts and alert items. This feature makes it
possible for the same alert item to be used in separate audits that may be examining different aspects of a
compliance problem.
Normal detection strategies produce only a single alert per investigation object. Each irregularity that is
found is added to this alert as an alert item. For example, each irregularity found in a purchase order item is
added as an alert item to a single alert for the purchase order.
Detection procedures are integrated into the lifecycle of an audit. This feature ensures that audit detection
strategies can be assigned and executed only at the appropriate phases in the life of an audit.
● You can create or edit a detection procedure only in the audit phases Initiated and Work Program Rejected.
In the Initiated phase, you can choose the audit detection strategy to use. In the Work Program Rejected
phase, you can respond to objections by adding a detection procedure or editing a task to choose a
different audit detection strategy.
● An audit detection strategy can be run only in the audit phases In Execution, Final Report Submitted, and
Final Report Rejected.
You create and edit strategies for audits in SAP Business Integrity Screening, just as with normal strategies. In
SAP Audit Management, you only choose and run detection strategies. These audit detection strategies must
have been prepared previously in SAP Business Integrity Screening.
In SAP Audit Management, you are responsible for ensuring that the detection strategy matches your audit.
That is, the investigation object type and detection object type match the data that is the subject of the audit.
The parameters for selecting data to examine are correct with regard to the audit, and so on. You can display an
audit detection strategy from a detection procedure and verify this information. But SAP Audit Management
cannot check that the strategy is optimal for the purpose.
Detection procedures let you integrate SAP Business Integrity Screening into your audits in SAP Audit
Management. This section describes the process for working with SAP Business Integrity Screening in the
context of an audit.
You have started an audit and want to use SAP Business Integrity Screening to examine relevant business data
for irregularities. How do you proceed?
1. Start by defining a detection strategy in SAP Business Integrity Screening for use in SAP Audit
Management.
You must define and activate such a strategy for each detection procedure that you create.
To define such a detection strategy, you use the standard tools of SAP Business Integrity Screening. You
set the Investigation Reason to specify that the strategy is for use in SAP Audit Management.
For more information, see Creating Detection Strategies.
2. In SAP Audit Management, create a detection procedure and use it to run the detection strategy. For more
information, see Create Detection Procedures [page 106] and Perform Detection Procedures [page 110].
Detection Information
● In a detection procedure, click its detection strategy and you will be directed to the detection strategy in
SAP Business Integrity Screening, where you can check or adjust selection and method parameters,
calibrate and optimize the strategy, activate the strategy, or make other changes.
● From the link in the Working Paper section, you can navigate to the working paper that contains the alerts
found by the detection task.
● In the Automatic Runs section, you can see how many times a mass detection has been run, using the SAP
Business Integrity Screening detection strategy specified in the task. Alerts can be created and inserted
into a working paper only if the detection strategy has been run.
If the Status column shows that there was an execution error during mass detection, then you can use the
log feature of SAP Business Integrity Screening to display the error messages. For more information, see
Analyze Mass Detection Log.
Procedure
SAP Audit Management allows you to use the business rules defined in SAP Process Control to retrieve and
analyze business data from a business system through an ad hoc query.
A business rule procedure is not restricted to one business rule. With a business rule procedure, you can use
any available business rules.
Prerequisites
To use the business rule procedure function, the following prerequisites need to be fulfilled.
Procedure
Field Description
4. Choose Save.
5. In the Controls section, specify the controls you want to test with the business rule procedure, if any.
Only those controls that are covered by the work package can be selected.
Use the work program spreadsheet template to upload business rule procedures.
Procedure
1. Open the Business Rule sheet in the work program spreadsheet template.
2. Choose a work package.
3. Enter business rule procedures. A row presents a business rule procedure.
○ Title
○ Description
Auditors perform the tasks outlined in the work programs and and document the results.
● Test procedures
To perform a test procedure, follow the steps in the procedure.
● Question procedures
Ask the auditee the prepared questions.
● Business rule procedures
See Perform Business Rule Ad Hoc Query [page 109].
● Detection procedures
See Perform Detection Procedures [page 110].
Context
You can execute any business rules with a business rule procedure. Every time you execute an ad hoc query
and get the query results, you can refresh the page and then choose another business rule to execute.
Procedure
In the Select Business Rule window, you can click on Show Filters to use the filters.
5. Select a target connector, namely the target business system in which the query will be performed.
When irregularities are identified through running a detection procedure based on the detection strategy, these
irregularities are recorded as alert items in a working paper of the detection procedure.
Note that you can run a detection procedure only when the audit is in one of the following statuses:
● In Execution
● Final Report Submitted
● Final Report Rejected.
1. Find the detection procedure you want to run in the Procedures section and click it.
The details page of the detection procedure shows information about the procedure including its status,
the detection strategy employed, related working papers, if any, and whether the procedure has been run
before. You can click the detection strategy to see its details and verify that the selection and detection
method parameters are correct.
2. Click Run to run the detection procedure. SAP Business Integrity Screening uses the detection strategy
assigned to the task to perform mass detection.
Each run is recorded as an entry in the Automatic Runs tab. You can click on the top-right of the tab to
get the current status of the runs you have launched.
Following the completion of the first run of a detection procedure, a working paper is automatically
generated, which can be found in the Working Papers section. Any irregularities found during each run are
recorded as alert items in the working paper. No duplicate alert items will be created. Alerts are
automatically assigned to the user who is responsible for the work package.
Note
If an error occurs during a run and is reported, you can use the SAP Business Integrity Screening log
transactions to display the error log produced. For more information, see Analyze Mass Detection Log.
You can also use the debugging facilities offered by SAP Business Integrity Screening. For more
information, see Testing and Debugging Detection Strategies in Simulated Mass Detection Runs.
Issues or irregularities found by performing a detection procedure are recorded as alert items in the working
paper of this procedure.
Process
1. The working paper lists the alert items generated by each run of the detection procedure. The columns of
the tables have the following meanings:
○ The first column identifies the business entity with respect to which an irregularity was discovered.
This business entity may be, for example, a vendor, a purchase order, or an insurance claim. All alert
items in a working paper pertain to the same type of business entity.
○ The Additional ID columns provide more information on the business entity, such as the name of a
vendor or the number of a purchase order item. The contents of these fields are tailored to the type of
business entity.
○ The Additional Date field shows the date of the business irregularity. The date may be the posting date
of a suspicious purchase order or the date on which a suspicious vendor master data change occurred.
○ The Status field shows the status of the alert item, as shown in the Finding. The status may be, for
example, Confirmed or Closed Without Investigation. You can set the status only in SAP Business
Integrity Screening, on the Decision tab in the alert item details.
2. Click an alert item to open the alert in SAP Business Integrity Screening. From the alert, you can navigate
to the alert item. You can use the investigative tools of SAP Business Integrity Screening to analyze the
alert item, document your work, and set the status in the Finding field. For more information, see
Investigation.
When you have set a finding for each alert item in the working paper, you can then determine whether a finding
in the audit is required.
After you have interviewed or inquired your auditee, you can evaluate the auditee's responses to the questions
you asked.
Procedure
1. Choose one of the following options depending on which app you work with.
My Ongoing Audits Select your audit, go to the Work Program and then open
your work package.
Audit scoring provides a quantitative assessment approach, which comes in when there are question
procedures in your audits.
The score of a question procedure is calculated by multiplying the rating and the weight, and the score of an
audit is calculated by summing up the scores of all the question procedures in the audit.
Max Score
Example
This example audit contains two scopes and each scope contains three questions. The rating scale is:
● 2
● 5
● 10
Question A-3 2 10 20
Question B-3 2 5 10
After performing an audit procedure, you can evaluate the effectiveness of the controls tested by the
procedure.
Prerequisites
Procedure
1. Choose one of the following options depending on which app you work with.
App Action
My Ongoing Audits Select your audit, go to the Work Program and then open
your work package.
You can document the audit work you have completed for each work package in the work program.
1. Find this audit in My Ongoing Audits, and navigate to the Work Program section and open a work package .
2. Choose the Work Done/Work Done Notes button, and type your notes.
3. After you finish, choose OK to save the notes.
After saving the notes, you can choose the Work Done/Work Done Notes button again to review and edit the
text. The notes will be visible to all users who have access to this audit.
If you process your work package offline, you can also enter your work done notes in a PDF file and send it back
to the system. For more information, see Processing Work Packages Offline [page 126].
In the review process, work package responsible persons go to the My Work Package app to submit their work
packages. The reviewers then review the submitted work packages in the app Review Work Packages and set
the work packages to Reviewed.
○ SUBMIT ○ Submitted
○ MARK_REVIEWED ○ Reviewed
After the work in a work package is completed, you can submit the work package for review.
Procedure
Procedure
Learn about the purpose of the attributes Finding Type, Finding Category, and Finding Ranking, as well as how
to configure them.
Finding Type
You can use finding types to classify findings by the risk areas.
Finding Category
You can use finding categories to indicate whether communication of a finding to the board is required and
what manner of communication should be taken.
● Board Relevant
● Non Board Relevant
Finding Ranking
● High
● Medium
● Low
You can build dependency between finding types and audit types.
When creating a finding, auditors can only choose from the finding types allowed for the audit type.
To build the dependency, use Customizing activity Configure Audit and Finding Type Dependency.
You can build dependency between finding rankings and audit types.
When ranking a finding, auditors can only choose from the finding rankings allowed for the audit type.
8.6.2 Finding ID
After a finding is successfully created, the system generates an ID for it. You can use this ID for reference
purpose. You can also change the pattern of how the ID is generated. For more information, see the Installation
Guide at http://help.sap.com/audit_s4. On the finding list, you can also change the ID of findings by adjusting
their sequence numbers in edit mode. The sequence number corresponds to the last digits of the finding ID.
You can change the ID of any finding in draft status. If there are actions under the finding, the part of the action
ID inherited from its parent also changes with the finding ID.
More Information
Context
You can create a finding at the audit level or the audit procedure level.
Procedure
1. Choose one of the following options depending on which app you work with.
2. Choose Create.
3. Enter the following information:
Field Description
Condition The factual evidence that the auditor found in the course
of the examination. The condition explains “what is or has
happened”.
Cause The reason the condition occurred. The cause is the differ
ence between what-is (condition) and what-should-be
(criteria).
4. Save.
Results
Next Steps
You can link the finding to risks and controls, upload attachments, and add an existing working paper.
If a finding is created at the audit level, you can link it to an audit procedure.
Procedure
Auditors communicate the findings with the auditee to seek acknowledgment that the findings are true and
accurate, and to allow the auditee to propose action plans for resolving the findings.
1. Submit findings
The auditors submit Draft findings to the auditee for review.
Note
If e-mail notification is enabled for this purpose, the auditee will receive an email notification with a PDF
file attached that presents the finding details.
2. Review findings
The auditee, usually the Executive Responsible, reviews the findings in the app My Findings.
○ If the auditee rejects the findings, the findings are sent back for rework.
○ If the auditee accepts the findings, the status of the findings becomes Open.
After findings are documented, you can develop action plans to address the findings.
SAP Audit Management enables collaboration between auditors and auditee in developing action plans, and
action plans can be marked with different statuses such as In Process, Completed, and Obsolete. You can
configure the action plan workflow using status schema.
1. Create action plan status schemas in Customizing activity Define Audit Status Schema.
SAP Audit Management provides two status schemas for action plans: DEFAULT and DFLT_ADTE.
See Action Plan Status Schema: DEFAULT [page 122] for more information.
2. Apply status schemas to audit types in Customizing activity Define Audit Types.
The following flowchart explains the Action Plan Status Schema DEFAULT.
Procedure
Field Description
Action Plan Responsible The person responsible for the action plan.
6. Save.
7. Select the newly created action plan to create sub-action plans and upload documents if needed.
Procedure
Field Description
Action Plan Responsible The person responsible for the action plan.
6. Save.
With the app My Action Plans,you can access, deal with and track down the action plans to which you are
assigned as the Action Plan Responsible from the point in time when they are submitted.
You can upload attachments, enter comments, and change status of action plans.
By setting an Open action plan to In Process, you indicate that they are starting to execute the action plan.
If email notification is enabled for this process, the Action Plan Responsible receives an email notification with
an attached PDF file that presents the action plan. In the PDF file, the Action Plan Responsible can set the
action plan to In Process or provide response. This will be sent back to the system via e-mail by choosing the
button Submit.
Note
You must use the same email account to receive and reply to this e-mail notification.
Escalate
When you as the Action Plan Responsible decide that one of the action plans under your responsibility
requires attention from the higher level or you need help in order to complete the action plan, you can escalate
it. All action plans that are open or in process can be escalated.
Respond
This function allows the Action Plan Responsible to keep the audit team up-to-date with their progress in
terms of the action plan execution. The Action Plan Responsible clicks the Respond button and provides
information. The audit team will be informed via email notifications.
The operations that are allowed for the Action Plan Responsible with the app can change depending on your
status schema configuration in the Customizing activity Define Audit Status Schema.
You can also change the ID of actions by adjusting their sequence numbers in edit mode. The sequence
number corresponds to the last digits of the action ID. You can change the ID of any action in draft status. If
there are child actions, the part of the action ID inherited from its parent also changes with the parent action ID.
If audit findings disclose a new risk, you can propose it to SAP Risk Management.
Prerequisites
Procedure
If the finding(s) are already assigned to an organzation, the risk is also assigned to this organization.
6. Go to the Analysis section to assess the likelihood level and impact of the risk.
7. Submit the risk.
If the findings carry action plans, the action plans are also proposed as treatments/responses to the risk.
Results
In the Risks Risk Proposal section of the finding(s), you can see the proposed risk.
By clicking on it, you will be redirected to the SAP Risk Management Proposed Risks .
Note
You can process audit work packages assigned to you using SAP Interactive Forms by Adobe.
This offline processing feature enables you to perform your audit work without having to log on to the SAP
Audit Management system. With SAP Interactive Forms by Adobe, you can enter work done notes, attach
working papers to a PDF document, and send them back to the system via e-mail.
Prerequisites
● A virtual host to the SMTP server has been created in your client with SAP Audit Management power user
information maintained on the logon data tab. Contact your system administrator to create the virtual
host. For more information, see the Online Manual under transaction SICF.
● You have installed and configured the Adobe Document Service (ADS). For more information, see the
Installation Guide for SAP Assurance and Compliance Software for SAP S/4HANA at http://help.sap.com/
audit_s4.
● You have installed a PDF software that supports XFA (XML Forms Architecture) content.
Procedure
1. Go to an initiated audit, prepare the work program, assign responsible persons to work packages, and
submit the work program.
After the audit manager approves the work program, individual work packages are sent to their responsible
persons as PDF attachments to the notification e-mails.
2. As a responsible person for the work package, you open the PDF file in your e-mail and perform your audit
as described in the work package.
3. If JavaScript is disabled in the PDF document, enable it.
4. To add working papers to the work package, click on the Attachments tab on the side panel, choose Add,
select the files, and choose Open.
5. You can also enter your work done notes in the Notes field.
6. After you finish processing the work package, send the PDF document back to the system using one of the
following methods:
○ If you are using an e-mail client, choose the Submit button in the PDF document. A reply e-mail window
opens with the updated PDF document attached. Send the e-mail back to the system.
○ If you are using a web browser, save the PDF document from the e-mail, attach it in the reply to the
notification you have received, and send it back to the system.
Note
Do not use the default recipient address when you send the reply. The correct recipient address
can be found in the configuration of the exit rule for inbound processing under transaction SO50.
Use the recipient address corresponding to exit name CL_GRCAUD_EMAIL_INBOUND.
If the e-mail is received successfully, the attachments and notes appear under the work package in SAP Audit
Management.
For more information about the offline processing feature, see Extending the Offline Processing Featurein the
SAP Audit Management Extensibility Guide.
You are able to reopen the work program of an audit in status In Execution to revise the work program.
To do this, click the Reopen Work Program button. The audit then changes to status Work Program Reopened
and can be accessed in Prepare Audits.
As an audit lead, you can modify the work program and submit it again for review and approval.
You can only add new work packages to the work program. Editing of existing work packages is not allowed,
nor is uploading work program using spreadsheets.
In the follow-up phase, auditors evaluate the adequacy, effectiveness, and the timelines of actions taken by
management on reported findings and recommendations.
In reviewing the evaluation result, the auditor determines whether management has implemented the
recommendations or accepted the risk of not implementing them.
Track Open Findings, Display Historical Findings,Track Open Action Plans and Display Historical Action Plans
come with the export function that allows you to export and download the complete list of open or historical
findings and actions. This facilitates the tracking of findings and action plans offline, for example, using a
spreadsheet tool.
To export findings and action plans, click the Export icon on top of the action list and choose the desired export
format.
To enable this function, you need to first maintain the file templates in scenario LST_ACTION in Customizing
activity under GRCAUD SAP Audit Management Basic Settings File Generation Maintain Templates for
File Generation . This scenario is offered in the default setting.
Note
The exported document contains the complete list of findings or actions and all relevant information,
regardless of the personalization and filters applied to the list.
The Track Ongoing Audits tile is available for the audit manager to track the current status of audits.
The Track Ongoing Audits screen lists the audits assigned to you as the audit manager. You can monitor the
overall progress of each audit, check the tasks performed, view the working papers, findings and reports that
have been created, and close the audit.
To perform other tasks as the audit manager, go to the Approve Audit Preparation or Approve Audit Report tiles.
Historical audits include canceled audits and audits that are closed after the final report is approved.
Use
Historical audits are read-only and can be accessed from the Display Historical Audits tile. You can view the
audits only under the audit group that your user is authorized to access.
Reopening Audits
Closed audits can be reopened to allow auditors to rework the audit, for example, to add new findings and
action plans.
You can reopen an audit in the Display Historical Audits tile. Once reopened, the audit are changed into the In
Execution status and can be found in the Track Ongoing Audits and My Ongoing Audits tiles. As an auditor, you
can add new working papers, create new findings and action plans, and submit new audit reports for review.
You can further reopen the work program of the reopened audit. For more information, see Reopen Work
Program [page 127].
You can monitor and track allOpen findings with the app Track Open Findings.
After evaluating how management has responded to the action plans and recommendations proposed in the
finding, you can close the finding or set it to obsolete as the case might be.
Edit findings
Here you can add attachments to a finding and change the Executive Responsible person.
Close findings
You can close a finding when all action plans under the finding are completed. A closed finding is removed from
the appTrack Open Findings. You can find it in the app Display Historical Findings and under the relevant audit in
Display Historical Audits .
Under certain circumstances, a finding may no longer be relevant to the audit. In this case, you have the option
to obsolete it. When you obsolete a finding, action plans under this finding with status In Process are set to
Obsolete. However, this does not change the status of completed action plans.
Raise issues
With a predefined connector, you can raise a finding as an ad hoc issue to SAP Process Control.
To do this, click the Raise Issue button, select a connector, and choose OK. Note that you can only raise one
issue per finding. Ad hoc issues can be accessed in the Ad Hoc Tasks section of My Home work center in SAP
Process Control.
If required, you can also create new action plans for an open finding with this app. Action plans created in Track
Open Findings need to be manually accepted by auditors. Open the draft action plan and choose Accept to set
the status to Open.
Note
You have to enable this functionality in Customizing activity Create Action Plans in Follow-Up Phase.
To complete an action plan, go to the Track Open Actions tile, select an action plan, and choose Complete. For
more information, see Tracking Open Actions [page 132].
With the app Display Historical Findings, you can display an overview list as well as detailed information of all
Closed and Obsolete findings which you have access to, and export the list to a spreadsheet.
Reopen findings
You can also reopen a historical finding, if needed. This allows the audit team and the auditee to continue
working on unfinished issues by adding more action plans. You can find reopened findings in Track Open
Findings.
With the app the Track Open Action Plans screen, you can track action plans in status Open and In Process.
The audit team can set Open action plans to In Process, indicating that Action Plan Responsible person needs
to start the execution of the action plans.
Based on the execution of an action plan, the audit team decide to set the action plan to Reasonably Controlled,
Follow-Up Required, or Completed accordingly.
When the responsibility of an action plan is shifted or the auditee requests more time to execute, the audit
team may need to modify the persons that take responsibility and extend the deadline of the action plan.
When an action plan is long overdue or requires attention from the management, you can escalate it. All action
plans that are Open and In Process can be escalated.
You can escalate an action plan to multiple levels. The escalation levels are maintained in the Customizing
activity Follow-Up Maintain Escalation Levels for Action Plans .
Historical action plans are action plans with the status Completed,Reasonably Controlled, Follow-Up Required,
or Obsolete.
You can access all historical action plans from the Display Historical Action Plans.
Historical action plans provide information about the management response to the action plans communicated
in the audit result. Internal auditors can use this information to decide whether follow-up audits are required.
You can reopen an action plan in status Completed, Reasonably Controlled, or Follow-Up Required, if additional
effort from the auditee is required.
Reopened actions are set back to the status Open and can be found in Track Open Action Plans.
During the reporting phase, auditors prepare draft and final audit reports and send them to the audit manager
for review. Final reports can only be submitted for review after the draft report has been approved by the audit
manager. Approved final reports can be issued to stakeholders to communicate the audit objectives, audit
scope, conclusions, recommendations, and action plans.
You can create audit reports for audits with one of the following statuses:
● In Execution
● Draft Report Approved
● Rework Draft Report
● Rework Final Report
You can create an audit report by uploading a local file or by generating it online using report templates.
Note
Before you start, complete the configuration settings in the Customizing activity Maintain Templates for
Generating Audit Reports.
You can edit the name of an audit report and delete a report before it is submitted for review.
If you are the audit lead, you can send the audit report to the audit manager for review by choosing the Submit
Draft Report or Submit Final Report button as the case may be.
You can only submit the final report after the draft report is approved.
More Information
As an audit manager, you review audit reports submitted to you in Approve Audit Reports and choose to
approve or reject them.
After you approve a draft report, the audit lead can proceed to prepare the final report and submit it for review.
An approved final report can be issued publicly to the stakeholders. You then have the option to track open
findings and close the audit.
When you reject a draft or final report, it will be sent back to the audit lead for rework. The audit lead can
modify the report and submit it again for review.
If e-mail notification is enabled, you can also receive an e-mail with the audit report attached as a PDF or Word
document. In the case of draft report, a PDF approval form can also be attached. You can approve or reject the
report directly within the PDF form.
When generating audit reports, you can choose a template of the IDOC - Interactive Audit Report type to
generate an interactive audit report. This type of Word report allows you to modify audit information directly in
the document and apply the changes in the system.
To review the content of an interactive audit report, download the document online or from your e-mail, modify
the fields where needed, save your document, and upload or send it back to the system via e-mail. You can
modify the following fields:
Note
You cannot create new findings or actions, or modify the ID of existing findings and actions in the
document. Any changes must be entered in the highlighted grey area.
As an audit lead, you can apply the changes in the audit report to the system by synchronizing the data. To do
so, open the audit report in My Ongoing Audits and choose Sync. Note that the Sync button is only available for
interactive audit reports.
More Information
After a final report is approved, the audit manager communicates the audit objectives and scope as well as
conclusions, recommendations, and action plans to the relevant stakeholders by issuing the final report.
Use
After you approve a final audit report in the app Approve Audit Reports, you can proceed to issue the final
report.
After you issue the final audit report for an audit, the status of the audit becomes Final Report Issued and the
audit can be closed.
A closed audit is read-only and no longer appears on in My Ongoing Audits or Track Ongoing Audits. You can
find all closed audits in Display Historical Audits.
Only the user assigned as CAE or the audit manager can close the audit.
You can still track the findings and actions under a closed audit. For more information, see Track Open Findings
[page 130]and Tracking Open Actions [page 132].
SAP Audit Management enables you to maintain working papers for your audits.
Key Features
Working papers are categorized and stored in different folders in the Working Paper section of an audit. SAP
Audit Management delivers the following four folders with each corresponding to a phase of an audit. Working
papers created in a specific phase are put in the corresponding folder.
● A – Planning
● B – Preparation
● C – Execution
● D – Reporting
You can manage the categories or create your own categories in Customizing activity Maintain Working Papers
Categories.
You can configure which folders are accessible to audits with which statuses in Customizing activity Define
Audit Status Schema.
You can create working papers for an audit from the draft status until it is closed or canceled.
Procedure
Note
You cannot delete a working paper that is being referenced, for example, by a finding.
Reviewers can leave review notes for working papers to provide their feedback. Auditors and reviewers can
have conversation over a review note by posting replies. When a review note is resolved, auditors need to mark
it as Cleared.
Note
Procedure
Procedure
You can mark a review note as Cleared to mean you have read and understand the review note and any issues in
the review note are resolved.
Procedure
You can view and edit a working paper without downloading it.
Prerequisites
● You have installed Microsoft Office applications on your desktop. The applications will be called up to open
working papers with.
For Mac OS, we recommend you use the latest version of Microsoft Office.
● Online editing of working papers is only available on the default client of your SAP Audit Management
system. It may not work if the frontend and the backend are deployed separately.
By enabling the versioning functionality, you can create multiple versions of a working paper.
Prerequisites
To enable or disable the versioning, use the Customizing activity Working Paper Management Enable
Version Management .
To create new versions of a document, simply upload a file with the same name. If the content of the new
document is the same as the existing one, the system does not create a new version.
If you disable the functionality after multiple versions are created for a document, these versions still exist in
the system and can be accessed.
You can delete those redundant versions of your working papers in bulk to save memory of your database using
the Customizing activity Working Paper Management Clean Up Working Paper Versions .
You cannot delete a working paper that is being referenced, for example, by a finding.
You can set a size limit for working papers using the Customizing activity Set Working Papers Size Limit.
SAP Audit Management provides checkpoints that you can apply to help ensure the quality of your internal
audit activities.
In Customizing activity Audit Quality Checkpoints, you can configure the application scenarios for a checkpoint.
● Action
The action decides when the checkpoint is triggered.
● Status Schema
The status schema decides to which audits the checkpoint is applied.
The Audit Management Overview app provides an analytical dashboard with interactive charts that present a
consolidated view of the internal audit across your organization.
Available Charts
Charts
Audits (Final Report Issued, Current Year) By Audit Group and Category
Audits (Final Report Issued, Current Year) By Quarter and Audit Group
Audits (Final Reports Issued, Current Year) By Audit Group and Rating
Audits (Final Report Issued, Previous Year) By Quarter and Audit Group
The chart Audits By Audit Phase and Audit Group only works when you have defined audit phase in Customizing
activity Define Audit Phases
Tooltips are displayed when you hover over the charts, such as over a bar of a bar chart, to help you understand
the data.
You can select the interactive charts to see the data in more detail. For example, the chart Action Plans by Audit
Group and Status shows the number of action plans in the form of a bar chart. If you select a bar, you'll be
navigated to a screen where the action plans represented by the bar are listed.
The following functions support you in handling personal data as well as archiving and deleting data.
Note
For more information, see the Security Guide on the SAP Help Portal.
Related Information
You can use this function to remove the user names from the system once the residence period has been
reached.
To remove the user names from business objects, call transaction Remove User Names
(ACS_DP_ANONYMIZATION) in the back-end system.
You have defined the residence period for each business object in Customizing activity Define Residence
Period.
Example
Depending on the structure of the business object, you can use this function to remove the Created By user
names, Last Changed By user names, or Executed By user names.
Note
For more information, see the detailed documentation in the back-end system.
To delete objects that are no longer referenced or no longer needed, call transaction Garbage Collector
(ACS_DP_GCO) in the back-end system
Prerequisites
You have defined the residence period for the simulated alert input data in Customizing activity Define
Residence Period.
Results
For more information, see the detailed documentation in the back-end system.
Application Log
You can display the application log for the Garbage Collector using transaction Display Data Protection Logs
(ACS_DP_LOG).
Related Information
Data archiving is used to remove mass data from the database that is no longer required in the system but
must be kept in a format that can be analyzed.
The following table shows the available archiving objects and their ILM objects:
Dependencies
Before archiving, the system checks if the preconditions for archiving data are met. Then, the write program
writes the data in an archive file. The delete program deletes the archived data from the database. It is still
possible to display this data in the archive file.
The SAP data archiving concept is based on the Archive Development Kit (ADK) using the Archive
Administration function (transaction SARA).
For more information, see Data Archiving in the ABAP Application System.
For more information, see the SAP Information Lifecycle Management (ILM) documentation on the SAP Help
Portal at http://help.sap.com.
You can use this function to display the data protection logs.
To display the application log, call transaction Display Data Protection Logs (ACS_DP_LOG) in the back-end
system.
Selection Parameters
You can filter the logs, for example, by the following criteria:
Note
To display the log for data archiving, choose the object ARCHIVING.
○ DELETION for data that has been deleted with the garbage collector
● External ID
Results
Examples for log messages that have been created for the subobject DELETION are:
Use
Personal data such as skill rating and uploaded photos remains in the system even after a user leaves the audit
team. With transaction GRCAUD_DEL_PERS_DATA or area menu Delete Skill Data, you can delete your personal
data and the data of other users provided you have the proper authorization. You can also use this functionality
to reset the skill rating of a user.
For more information about the menu, see the documentation for the transaction.
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.