AC10 To 10 1 Upgrade
AC10 To 10 1 Upgrade
AC10 To 10 1 Upgrade
4 PUBLIC
1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 SAP Notes for Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 SAP Fiori Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 Configuration Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Master Data - BC Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 Transactional Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
5 System Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 1:
This guide is intended for customers who currently use SAP Access Control 10.0 and wish to upgrade to SAP
Access Control 10.1.
Purpose
This guide describes how to upgrade SAP Access Control 10.0 to SAP Access Control 10.1. The document
provides the following information.
Constraints
This Upgrade Guide is a standalone document; it has the following list of constraints.
● This guide discusses the upgrade process of the SAP Access Control 10.0 application to SAP Access Control
10.1. Any attempt to use this guide for other product versions is not supported
.
This guide does not provide information for the following uses:
Table 2:
For more information regarding SAP Fiori apps, see SAP Fiori for SAP Access Control 10.1 http://help.sap.com/
grc-ac .
This guide discusses how to convert the existing SAP Access Control 10.0 application to SAP Access Control 10.1.
The upgrade process involves the conversion of the data types listed below.
Use
Configuration data includes the configuration parameters that you specify within Customizing (IMG transaction
SPRO).The following new Customizing activities are available as of SAP Access Control 10.1:
Table 3:
Maintain settings for Simplified Ac Governance, Risk, and Compliance Access Control User Provisioning Simplified Access Request Main
cess Request processing
Sections
Maintain settings for Simplified Ac Governance, Risk, and Compliance Access Control User Provisioning Simplified Access Request Main
cess Request processing
Labels
Maintain settings for Simplified Ac Governance, Risk, and Compliance Access Control User Provisioning Simplified Access Request Main
cess Request processing
Page
Maintain settings for Simplified Ac Governance, Risk, and Compliance Access Control User Provisioning Simplified Access Request Main
cess Request processing
Reasons
Disable Link Functionality in Attach Governance, Risk, and Compliance General Settings Disable Link Functionality in Attachments and Links
ments and Link
Configure Side Panel for My Process Governance, Risk, and Compliance General Settings UI Settings Configure Side Panel for My Process
Define Audit Groups Governance, Risk, and Compliance Common Component Settings Internal Audit Management Define Au
Maintain Firefighter ID Role Name Governance, Risk, and Compliance Access Control Emergency Access Management Maintain Firefighter
Per Connector
Per Connector
Additional Rule Upload Governance, Risk, and Compliance Access Control Access Risk Analysis SoD Rules Additional Rule Up
Organization Rule Creation Wizard Governance, Risk, and Compliance Access Control Access Risk Analysis SoD Rules Organ
Wizard
Configure Attributes for Role Search Governance, Risk, and Compliance Access Control User Provisioning Configure Attributes fo
Criteria in Access Requests
Access Requests
More Information
● For more information about configuration, see the Maintain Configuration Settings Guide for SAP Access
Control at https://service.sap.com/instguides Analytics Governance, Risk, and Compliance Access
Control .
● For more information about each IMG activity, see the IMG documentation that accompanies each IMG
activity.
The BC Sets below are new to SAP Access Control 10.1 and must be activated as part of the SAP Access Control
10.0 to 10.1 upgrade.
Table 4:
For more information about activating BC sets, see the SAP Access Control , SAP Process Control , and SAP Risk
Management 10.1 Installation Guide at https://service.sap.com/instguides Analytics Governance, Risk,
and Compliance Access Control .
Use
Transactional data are transaction-based records related to the audit trail, workflow items, and so on. If any
changes are necessary for transactional data, the system handles them automatically using XPRA during the SAP
Access Control 10.1 deployment.
More Information
For more information about data conversion, see the SAP Help Portal at http://help.sap.com/
saphelp_bpc70sp02/helpdata/en/84/29b0127a6011d3b505006094192fe3/frameset.htm.
Use
Before you can begin the upgrade process to GRCFND_A V1100 SP14, NetWeaver 7.40 SP13 is required. For more
information, see SAP Note 2298322..
More Information
For more information about SAP NetWeaver, see the SAP Help Portal at http://help.sap.com/netweaver
Use
To verify your data after the upgrade, we recommend that you perform the following list of tasks:
More Information
For more information about system logs, see the SAP Help Portal at http://help.sap.com/saphelp_bpc70sp02/
helpdata/en/1f/83119f4bc511d189750000e8322d00/frameset.htm.
Use
Upgrading from SAP Access Control 10.0 to SAP Access Control 10.1 is a same-box upgrade process. To perform
a system upgrade, complete the following steps.
Procedure
1. Close all open workflow instances and all open survey instances.
2. Back up the AC 10.0 system.
3. If used, delete all Datamart data.
4. Upgrade the SAP Access Control system from SAP NetWeaver 7.02 to SAP NetWeaver 7.40 SP02.
Caution
It is mandatory to apply SAP Note 1814403 after installing SAP NetWeaver 7.40 SP02 to ensure that the
NetWeaver Business Client (NWBC) is working properly.
5. Upgrade the SAP NetWeaver Portal 7.0 EHP1 to SAP NetWeaver Portal 7.0 EHP 2 SP06.
6. Install the GRC 10.1 component GRCFND_A_V1100 and the latest SAP Access Control support packages.
Note
■ For more information, see the SAP Access Control , SAP Process Control , and SAP Risk Management 10.1
Installation Guide at https://help.sap.com/grc-ac Installation and Migration Information.
Note
Alternatively, you can use the SAP NetWeaver Business Client (NWBC 4.0) instead of the SAP NetWeaver
Portal package.
For more information, see the SAP Access Control , SAP Process Control , and SAP Risk Management 10.1
Installation Guide at https://help.sap.com/grc-ac Installation and Migration Information .
13. If applicable, deploy the GRC10.0 Plug-in (RTA) package for SAP Access Control 10.1 in the ERP system.
See the following table for the GRC Plug-in packages for the different ERP/NW releases.
Note
For more information about backwards compatible plug-ins, see SAP Note 1821368 Inst/Upgrade
GRCFND_A V1100 on NW740.
14. Use transaction SICFto activate NWBC and Web Dynpro services beginning with the grpc and grfn, at /default
host/sap/bc/nwbc, /sap/public/, /sap/bc.
15. If you want to use SAP Risk Management (RM) and SAP Process Control (PC), you may need to activate the
RM and PC services as well.
■ For more information, see the SAP Access Control 10.1, Process Control 10.1, and Risk Management 10.1
Installation Guide at https://help.sap.com/grc-ac Installation and Migration Information.
More Information
For more information, see the SAP Access Control , SAP Process Control , and SAP Risk Management 10.1
Installation Guide at https://help.sap.com/grc-ac Installation and Migration Information. .
After completing the upgrade, you must perform the following list of post-upgrade tasks:
For SAP Access Control system aliases, use aliases SAP-GRC (foundation application) and SAP-GRC-AC.
If you want to launch SAP NetWeaver Business Client (NWBC) using SAP GUI, you need to assign users the role
SAP_GRC_NWBC using transaction SU01.
Use
Ensure that all SAP Access Control 10.1 custom model roles contain the authority of display regulation. To do so,
follow the procedure below:
Procedure
For information about Business Configuration Sets, see the SAP Access Control , SAP Process Control , and SAP
Risk Management 10.1 Installation Guide at https://help.sap.com/grc-ac Installation and Migration
Information .
Use
In order to use some of the new functionality in SAP Access Control 10.1, such as the Remediation View in SAP
Access Risk Analysis, an SAP NetWeaver Gateway connection must be established. Follow these steps to
maintain or verify the connector.
Procedure
1. Logon to an SAP NetWeaver system and access the SAP Reference IMGas follows: from the SAP Easy Access
menu, choose Tools Customizing IMG Execute Project (transaction SPRO) .
Caution
Be sure to specify the proper RFC Type, client, and user information using the naming convention:
4. If you are using Single-Signon, choose Define Trust for SAP Business Systems. Complete the fields with
information you provided in the Step 3.
Note
This step only applies if you are using Single-Signon.
5. Choose Manage SAP System Aliases to create the system alias for the RFC destination that you created in
Step 3.
6. Choose New Entries and enter the following values:
Table 6:
SAP System Alias Enter the name of the RFC destination that you created in
Step 3.
RFC Destination Enter the name of the RFC destination that you created in
Step 3.
Software Version Choose the value DEFAULT from the drop down list.
Table 7:
More Information
For more information, see the SAP Help portal at http://help.sap.com and search for: SAP NetWeaver Gateway
Developer Guide. Then choose OData Channel Basic Features Service Life-Cycle Activate and Maintain
Services .
Use
More Information
For more information about custom menus, see the SAP Help Portal at http://help.sap.com/saphelp_bpc75/
helpdata/en/3b/b5df48130f44fb8e9537701f09c960/frameset.htm.
Use
If you had any open workflow items before the upgrade, make sure that you restart any items that were not
completed.
For more information about workflow administration, see the SAP Help Portal at http://help.sap.com/
saphelp_banking463/helpdata/en/fb/135a0e457311d189440000e829fbbd/frameset.htm.
Use
The following functional roles have been modified for SAP Access Control 10.1:
Table 8:
Note
If you copy these roles, you must modify them according to your business needs.
More Information
For more information and to see the additional authorization objects added to existing roles, see theSecurity
Guide for SAP Access Control 10.1 / Process Control 10.1 / Risk Management 10.1 at https://help.sap.com/grc
choose your application Security Information Security Guide.
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).