P-CO-R Assignment

PDF download from SAP Help Portal:

http://help.sap.com/saphelp_mic10/helpdata/en/b2/03585f6a5b4da4bef665c4f5dbd72f/content.htm
Created on August 28, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.

Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 3

Table of content
1 P-CO-R Assignment

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 3

!--a11y-->

1 P-CO-R Assignment
Use
In the central process catalog, you assign one or more control objectives (CO) to a process (P). By doing so, you define the objectives of the process steps
defined as controls in that process. You then assign one or more risks (R) to the combination of process and control objective. A risk is a potential event that
adversely impacts the desired outcome of a control objective.

Prerequisites
In Customizing for MIC under Edit Attributes Attributes with Dependent Attributes , the power user has created control objective categories and one or
more control types for each control object category.

Features
For each control objective, you select a control objective category that has been created in Customizing for MIC. The control objective category determines
which control types an organizational unit can later enter as an attribute for a control when accepting processes and documenting controls.
For each risk, you specify which condition could cause the risk to come into play and which consequence this could have. Furthermore, you can specify
what would be the qualitative impact of the risk (such as negligible, minimal, immense). You can define the possible values in Customizing under Edit
Attribute Values .
The validity periods of the process, control objective, and risk must be compatible. This means that the validity period of a control objective must fall within
that of the process, and the validity period of the risk must fall within that of the control objective.

Example
Process: Order processing
Control objective: Only authorized transactions are posted
Risk: The transaction is not reviewed conscientiously

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 3