0% found this document useful (0 votes)
21 views

Sizing Guide For SAP Process Control

Uploaded by

minerva.paredes
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
21 views

Sizing Guide For SAP Process Control

Uploaded by

minerva.paredes
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

1/27/2024

Sizing Guide for SAP Process Control


Generated on: 2024-01-27 16:30:39 GMT+0000

SAP Process Control | 12.0 SP22

PUBLIC

Original content: https://help.sap.com/docs/SAP_PROCESS_CONTROL/74fc088a06694c7cad380378ce809cd4?locale=en-


US&state=PRODUCTION&version=12.0.22

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
1/27/2024

Introduction
SAP Governance, Risk and Compliance (GRC) solutions offer your organization a preventive, real-time approach to governance,
risk, and compliance. Automated risk and compliance monitoring activities can help you prevent risk events and compliance
violations, helping you protect the value of your organization.

SAP Process Control 12.0 is a SAP GRC product, which provides an end-to-end solution for documenting, evaluating, monitoring,
reporting, and certifying the status of internal controls within an enterprise. Process Control supports better management of
processes by automating previously manual and time-consuming tasks while increasing reliability and transparency.

SAP Process Control 12.0 is powered by the SAP NetWeaver® platform. SAP NetWeaver uni es technology components into a
single platform, allowing organizations to reduce IT complexity and obtain more business value from their IT investments. It
provides the best way to integrate all systems running SAP or non-SAP software. SAP NetWeaver also helps organizations align
IT with their business. With SAP NetWeaver, organizations can compose and enhance business applications rapidly using
enterprise services. As the foundation for enterprise service-oriented architecture (enterprise SOA), SAP NetWeaver allows
organizations to evolve their current IT landscapes into a strategic environment that drives business change.

This guide provides guidelines and rules for sizing SAP Process Control in your environment. Sizing is the process of translating
business requirements into the overall hardware requirements (such as physical memory, CPU processing power, and network
capacity) needed to implement the solution. The guide describes the steps of this process and explains the factors that
in uence performance and hardware requirements.

Functions of SAP Process Control


SAP Process Control provides a series of features including control documentation, control evaluation, certi cation, and
reporting and analysis, among other features. SAP Process Control offers the following capabilities:

Control Documentation
SAP Process Control supports a exible environment for setting up corporate master data, which includes the following
categories:

Organization structure: A multilevel hierarchy showing all organizations within the scope of internal controls
management.

Process catalog: A catalog of key business processes, as well as underlying sub-processes and associated controls,
created in hierarchical form.

Account groups: A list of the key nancial account groups and their related nancial assertions.

Control objectives and risks: A comprehensive, hierarchical catalog of control objectives and associated risks relevant to
compliance.

Entity-level controls: A catalog of central management controls, which may be classi ed by groups conforming to the ve
COSO (Committee of Sponsoring Organizations) components.

Policy Lifecycle: A policy library allowing users to maintain policies and execute policy reviews and approval processes.

Control Evaluation
SAP Process Control includes the following principal types of evaluation activity:

This is custom documentation. For more information, please visit the SAP Help Portal 2
1/27/2024
Assessments

Process Control provides a survey capability, which enables users to assess the design of sub-processes and controls, or
perform self-assessments on a periodic basis. If the assessment results in a de ciency, the solution supports issue
creation, remediation activities, and subsequent reassessment.

Effectiveness Testing

Process Control provides two methods for testing the effectiveness of controls – manual testing using test plans, and
automated testing using system rules and programs.

Manual testing method

Auditors or other testers use test plans from a repository to manually perform periodic tests of controls and
follow-up remediation actions if required.

Automated testing method

Controls are automatically tested on a predetermined schedule using system-driven rules.

Automated control monitoring

Process Control supports monitoring controls, which allow the tracking of non-compliant business events in an ERP
system through a combination of automated programs and exception reports. The system also supports the ability to
run ad hoc data queries for data retrieval, and to convert them into new controls.

Planning and Scheduling

Central to the evaluation activities is the ability to create an evaluation plan, which includes speci cation of the test time
frame, organizations involved, and type of evaluation.

Policy distribution

Policy managers can distribute policy acknowledgments, quizzes, and surveys to employees, requesting
acknowledgment.

In SAP Process Control, all evaluation activities are governed by a set of robust work ows and noti cations. Based on
evaluation schedules, users are automatically noti ed through work ow tasks which cover test performance, issue
management, remediation and retesting.

Certi cation
To support regulatory requirements, SAP Process Control provides the process of sign-off, which is a formal process of
attestation by organization owners and officers of the company on the state of internal controls. Certi cation is achieved using
a combination of sign-off surveys and work ows, and provides historic period reporting for audit requirements.

Reporting an Analysis
SAP Process Control provides detailed and exible reporting features that enable users to gain full visibility into the control
environment and make data-driven decisions. It supports a catalog of standard reports, which cover areas such as master data
setup, evaluation activities, audit logs and authorization analysis. All reports come with selection criteria, export and print
functionality, and drilldown capability for ease of use.

Architecture of SAP Process Control


GRC solutions are an add-on (software component GRCFND_A) to SAP NetWeaver 7.40 (ABAP) that allows you to use all
databases and operating systems supported by the SAP Web Application Server.

This is custom documentation. For more information, please visit the SAP Help Portal 3
1/27/2024

SAP Process Control Architecture

Integrated scenarios, principally between SAP Access Control and SAP Process Control, require you to have both applications
activated on the same SAP client (SAP Access Control resides in the same software component as SAP Process Control and
SAP Risk Management). Furthermore, GRC Plug-In Adapters are required for standard integration of SAP/non-SAP systems
and SAP Access Control.

 Note
Additional extensions (not considered in this initial sizing) are also available, including Identity Management Solutions
integration, LDAP user repositories integration, non-SAP systems provisioning, and SAP NW Enterprise Portal provisioning
integration, among others.

Factors that In uence Performance


This is custom documentation. For more information, please visit the SAP Help Portal 4
1/27/2024
The following factors can impact the performance:

HANA database use. Refer to the following for more information:

Suite on HANA memory sizing: SAP Note 1872170

Sizing for SAP Suite on HANA: SAP Note 1793345

SAP HANA 1.0 Sizing SAP in-Memory Database: SAP Note 1514966

Master data volume (for example, size of the central risk and control matrix, subprocesses and controls assigned to
organizations)

Transaction data volume

Con guration settings (for example, activation or deactivation of the report buffer)

Number of concurrent users

Sizing Fundamentals and Terminology


SAP provides general sizing information on http://www.sap.com/sizing . For the purpose of this guide, we assume that you are
familiar with sizing fundamentals. This section explains the most important sizing terms, as these terms are used extensively in
this document.

Sizing
Sizing means determining the hardware requirements of an SAP application, such as network bandwidth, physical memory, CPU
processing power, and I/O capacity. The size of the hardware and database is in uenced by both business aspects and
technological aspects. This means that the number of users using the various application components and the data load they
put on the server must be taken into account.

Benchmarking
Sizing information can be determined using SAP Standard Application Benchmarks . Released for technology partners,
benchmarks provide basic sizing recommendations to customers by placing a substantial load upon a system during the testing
of new hardware, system software components, and relational database management systems (RDBMS). All performance data
relevant to the system, user, and business applications are monitored during a benchmark run and can be used to compare
platforms.

SAPS
The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the performance of a system
con guration in the SAP environment. It is derived from the Sales and Distribution (SD) Benchmark, where 100 SAPS is de ned
as the computing power to handle 2,000 fully business processed order line items per hour. (For more information about SAPS,
see http://www.sap.com/benchmark → Measuring in SAPS).

Green eld Sizing


Green eld sizing refers to the sizing approach that provides statements about platform-independent requirements of the
hardware resources necessary for representative, standard delivery SAP applications. The initial sizing guidelines assume
optimal system parameter settings, standard business scenarios, and so on.

Expert Sizing
This is custom documentation. For more information, please visit the SAP Help Portal 5
1/27/2024
Expert Sizing refers to a sizing exercise were customer-speci c data is analyzed and used to provide more detail for the sizing
result. The main objective is to determine the resource consumption of customized content and applications (not SAP standard
delivery) by comprehensive measurements. More information can be found here .

Con guration and System Landscaping


Hardware resource and system con guration greatly depend on the requirements of the customer-speci c project. This
includes the implementation of distribution, security, and high availability solutions by different approaches using various third-
party tools. In the case of high availability through redundant resources, for example, the nal resource requirements must be
adjusted accordingly.

Initial Sizing for SAP Process Control


This section describes the procedure for sizing SAP Process Control.

Assumptions
This section describes the assumptions used when sizing Process Control.

The following performance-in uencing parameters in Process Control have been turned off:

Report buffering

Table logging

 Note
These requirements are only to create a standard environment for determining the sizing data. In your production
environment we recommend you enable both reporting buffering and table logging.

Sizing Guideline for SAP GRC Process Control 12.0


The sizing results described in this section were obtained by measuring the following scenarios:

Refreshing the work inbox

Creating plan for manual testing

Managing organizations

The results include memory usage and the minimum number of SAPS required for supporting the corresponding number of
users.

 Note
Switching on the shared objects memory will improve the performance for creating plans.

Refreshing the Work Inbox


In this scenario, users open their work inbox and manipulate work items relevant to them.

This is custom documentation. For more information, please visit the SAP Help Portal 6
1/27/2024

Procedure
1. Choose My Home Work Inbox Work Inbox .

2. Choose the Refresh link.

The inbox has been refreshed.

Memory requirement: 63 GB of Disk Space and Network speed of .02 Mbits /sec.

Following table represents the technical information based on various tests.

Category for CPU Requirements CPU Requirements Memory Requirements Memory Requirements
Enterprises (ABAP) (HANA) ABAP HANA

1000 scenarios per hour 1150 SAPS 1150 SAPS .5 GB RAM .03 GB RAM

2000 scenarios per hour 2300 SAPS 1150 SAPS .9 GB RAM .05 GB RAM

5000 scenarios per hour 3450 SAPS 2000 SAPS 2.3 GB RAM .13 GB RAM

X-Large (more than 700 Contact SAP or your hardware partner


users)

Creating Plan for Manual Testing


In this scenario, users create plans for manual testing and assessments using the Planner application.

Procedure
1. Choose Assessment Assessment Planning Planner .

2. Click the Create button.

3. Complete the wizard to creating a new plan.

4. Click the Activate Plan button.

Memory requirement: 103 GB of Disk Space and Network speed of .006 Mbits /sec.

Following table represents the technical information based on various tests.

Category for CPU Requirements CPU Requirements Memory Requirements Memory Requirements
Enterprises (ABAP) (HANA) ABAP HANA

1000 scenarios per hour 1150 SAPS 1150 SAPS 7 GB RAM 3 GB RAM

2000 scenarios per hour 2300 SAPS 2300 SAPS 14 GB RAM 5 GB RAM

5000 scenarios per hour 4600 SAPS 3450 SAPS 34 GB RAM 14 GB RAM

X-Large (more than 700 Contact SAP or your hardware partner


users)

Managing Organizations
This is custom documentation. For more information, please visit the SAP Help Portal 7
1/27/2024
In this scenario, organization owners manage relevant organizational data.

Procedure
1. Choose Master Data Organizations Organizations .

2. Click the Add button and select Create new organization in the dialog that appears.

3. Fill in all required elds.

4. Click the Save button.

Memory requirement: 3.8 GB of Disk Space and Network speed of .009 Mbits /sec.

Following table represents the technical information based on various tests.

Category for CPU Requirements CPU Requirements ABAP Memory [GB] HANA Runtime Memory
Enterprises (ABAP) (HANA) [GB]

1000 scenarios per hour 1150 SAPS 1150 SAPS 1.4 GB RAM .03 GB RAM

2000 scenarios per hour 2300 SAPS 2300 SAPS 2.9 GB RAM .07 GB RAM

5000 scenarios per hour 5750 SAPS 5750 SAPS 7.1 GB RAM .16 GB RAM

X-Large (more than 700 Contact SAP or your hardware partner


users)

Miscellaneous
This section describes the resources available related to sizing procedures and guidelines, as well as benchmark and installation
guides.

General Sizing
https://www.sap.com/about/benchmark/sizing.html

Expert Sizing
https://www.sap.com/about/benchmark/sizing.html

Benchmarking
http://www.sap.com/benchmark

This is custom documentation. For more information, please visit the SAP Help Portal 8

You might also like